xfs
[Top] [All Lists]

Re: Remounting read-only forces filesystem shutdown

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: Remounting read-only forces filesystem shutdown
From: Steve Lord <lord@xxxxxxx>
Date: Wed, 12 Apr 2006 21:09:29 -0500
Cc: Onis <onion@xxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <20060413100839.C1334248@wobbly.melbourne.sgi.com>
References: <20060412203719.GA22528@virasto.com> <20060413100839.C1334248@wobbly.melbourne.sgi.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 1.5 (X11/20060313)
Hi Nathan,

I have seen this too, and it is definitely on a system which reports
no barrier support in the devices. Shutdown ends up with exactly
this error - running 2.6.17-rc1 from Linus's git tree as of a
couple of days ago.

Steve

Nathan Scott wrote:
On Wed, Apr 12, 2006 at 11:37:19PM, Onis <onion@xxxxxxxxxxx> wrote:
Hi!

Hi there Onion,

When remounting XFS filesystem read-only it causes xfs_force_shutdown and
filesystem is unreadable. After umount/mount it is back again. I have
2 partitions with xfs. Both of them are affected. Problem does not occur
when using Debian's stock kernel. xfs_check does not report any error.

This impacts Debian shutdown script, so that system cannot shutdown
properly. Shutdown process just hangs until reset button pressed.

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?

thanks.



<Prev in Thread] Current Thread [Next in Thread>