[Top] [All Lists]

Re: umount doesn't seem to really unmount

To: Linux fs XFS <xfs@xxxxxxxxxxx>
Subject: Re: umount doesn't seem to really unmount
From: Stefan Ring <stefanrin@xxxxxxxxx>
Date: Mon, 27 Aug 2012 08:47:29 +0200
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=uplKRNi8Qw5qhFBQmeQrKW6PDSb1dYLaCEbSlAMZ7rg=; b=S6icAviqGZynxrob9eaBU/Gag2Etp8y+i96KfsXyDkRcpzC8ShX8s7bI3SO8OWQtiW Wfb3amHCwX9pOj2+1DKLWh32jAm2bnms7ZU40zMpL20/sTd707dSNxO8HMFNE6hi4Y3U eQ7UlgHmvKXMM7/Ro86DecX15lp6Qojz/ZksnKeN+jcK1ThSg2o+SbX3Gzn4WeZNEh99 cl7KPO+RlgxB35a/0Vafc0mu+YXYSOUmfjtR4Ufo1/7D062dp3ukgxH9mbN686ZH3b/h 0nahVmOWI93iexOL377FSvv63/1cD4uabUk0WZeIb+pvbBN/hbshh9yUw5OC+Fn6DLwF j/7w==
In-reply-to: <1104CDC2-47D2-40CF-8294-A17E33125D54@xxxxxxxxxxx>
References: <CAAxjCEwdYbcDoUvcAV1n8281HCCvrCvReaG2oM5+h+WV5yDZvA@xxxxxxxxxxxxxx> <1104CDC2-47D2-40CF-8294-A17E33125D54@xxxxxxxxxxx>
> Do you have barriers on and does iscsi pass them through to the target, and 
> does the target propagate them to the disk itself?

Regardless of the barriers, it doesn't explain this:

$ sudo mount -o barrier=1,inode64 /dev/mapper/vg_xfs2-lvxfs1 /xfs1
$ sudo umount /xfs1
$ sudo xfs_logprint /dev/mapper/vg_xfs2-lvxfs1
xfs_logprint: /dev/mapper/vg_xfs2-lvxfs1 contains a mounted and
writable filesystem
    data device: 0xfd01
    log device: 0xfd01 daddr: 83882016 length: 81912

It also happens in kernel 3.4.3-1.fc17. There are no other machines
which access the iSCSI target.

Right after boot, I can mount and umount it all that I want, and it
will work normally, i.e., say "Mounting Filesystem / Ending clean
mount" in dmesg, xfs_logprint NOT saying "... contains a mounted and
writable filesystem".

As crazy as that sounds, I've just found out what triggers the
situation. The weird behavior only manifests itself after this:

$ sudo service mysqld start

>From then on, it behaves as described earlier. Not that mysqld has
anything to do with XFS. It's just the plain package from Fedora, with
everything in the default place on the root filesystem, which is ext4.
As I've just found out, the behavior even returns to normal when I
shut down mysqld. So for now, my workaround is shutting down mysqld
myself before rebooting.

I'll try and see if this is easily reproducible inside a clean F17
install inside a KVM guest.

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