| To: | Nathan Scott <nathans@xxxxxxx> |
|---|---|
| Subject: | Re: Remounting read-only forces filesystem shutdown |
| From: | Onis <onion@xxxxxxxxxxx> |
| Date: | Thu, 13 Apr 2006 21:28:25 +0300 |
| Cc: | Steve Lord <lord@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20060413122138.A1338954@xxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <20060412203719.GA22528@xxxxxxxxxxx> <20060413100839.C1334248@xxxxxxxxxxxxxxxxxxxxxxxx> <443DB2D9.7070706@xxxxxxx> <20060413122138.A1338954@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
On Thu, Apr 13, 2006 at 12:21:38PM +1000, Nathan Scott wrote: > On Wed, Apr 12, 2006 at 09:09:29PM -0500, Steve Lord wrote: > > >> To repeat it, just do "mount -o remount,ro /mnt". > > > > > > Ah, I think I see the problem - looks like we can enable write > > > barriers accidentally during a remount,ro without checking to > > > see if the drive likes that idea. Ugh. > > > > > > Just to be sure - when you initially mounted the filesystem (rw), did > > > you get a dmesg message saying "disabling write barriers" or words to > > > that effect? Yes, dmesg says: Filesystem "md0": Disabling barriers, not supported by the underlying device > This patch to fs/xfs/xfs_vfsops.c should fix that right up... I'll get > it merged in asap. Looks like the only way to catch some problems is > to switch things on by default. ;) This definitely fixes the problem. Now I can boot and leave filesystem clean! Thanks! - Onion |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS), Jan Engelhardt |
|---|---|
| Next by Date: | Re: howto preallocate to minimize fragmentation, Chris Wedgwood |
| Previous by Thread: | Re: Remounting read-only forces filesystem shutdown, Nathan Scott |
| Next by Thread: | Bug-Report xfs_inode.c, Andreas G. Filzer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |