| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: xfs_repair unable to repair a corrupt filesystem |
| From: | Ethan Benson <erbenson@xxxxxxxxxx> |
| Date: | Sun, 23 Feb 2003 18:39:41 -0900 |
| In-reply-to: | <20030224033309.GA20260@lithium.sta.man.ac.uk> |
| Mail-copies-to: | nobody |
| Mail-followup-to: | linux-xfs@xxxxxxxxxxx |
| References: | <20030223081255.GA14077@lithium.sta.man.ac.uk> <20030223215931.GA798@frodo> <20030224033309.GA20260@lithium.sta.man.ac.uk> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
On Mon, Feb 24, 2003 at 03:33:09AM +0000, Russell G. Howe wrote: > On Mon, Feb 24, 2003 at 08:59:31AM +1100, Nathan Scott wrote: > > > There was an XFS problem in syncing when remounting read-only > > (which happens just before reboot), which was fixed earlier this > > year - it frequently affected /var because that is always very > > active during shutdown - this fix might help you if you upgrade. > > Hm, I didn't realise all filesystems were remounted ro, I thought all > but / were unmounted and then only / was remounted ro. Oh well you learn they are. perhaps the readonly fix could also affect a plain umount as well. -- Ethan Benson http://www.alaska.net/~erbenson/
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_repair unable to repair a corrupt filesystem, Russell G. Howe |
|---|---|
| Next by Date: | Re: xfs_repair unable to repair a corrupt filesystem, Nathan Scott |
| Previous by Thread: | Re: xfs_repair unable to repair a corrupt filesystem, Russell G. Howe |
| Next by Thread: | Re: xfs_repair unable to repair a corrupt filesystem, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |