| To: | Simon Matter <simon.matter@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS shutdown with 1.3.0 |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | 05 Sep 2003 10:51:32 -0500 |
| Cc: | Nathan Scott <nathans@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <2588.10.1.200.117.1062753733.squirrel@imap01.ch.sauter-bc.com> |
| Organization: | |
| References: | <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> <20030902071613.GB1378@frodo> <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> <20030905052032.GD1126@frodo> <2588.10.1.200.117.1062753733.squirrel@imap01.ch.sauter-bc.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
There's no simple way... probably the easiest way, assuming you generally use default mkfs options, and an internal log, is to check whether the internal log is in the middle ag. If so, it hasn't been grown. If it's located in the first half of the filesystem, then it has been grown. -Eric On Fri, 2003-09-05 at 04:22, Simon Matter wrote: > Unfortunately the problem looks like a timebomb to me. Is there a way to > find out whether a filesystem has ever been grown? This would help me to > find out whether the growing was the culprit here. > > Simon -- Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc. 651-683-3102 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: geez, Simon Matter |
|---|---|
| Next by Date: | [Bug 278] New: xfs_growfs crashes with kernel bug for negative grow sizes, bugzilla-daemon |
| Previous by Thread: | Re: XFS shutdown with 1.3.0, Simon Matter |
| Next by Thread: | Re: XFS shutdown with 1.3.0, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |