xfs
[Top] [All Lists]

Re: Unmount Didn't; Clues?

To: dcox@xxxxxxxxxx
Subject: Re: Unmount Didn't; Clues?
From: Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 29 Mar 2001 08:36:16 +1000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: Your message of "Wed, 28 Mar 2001 14:45:49 EST." <3AC23F6D.60E56609@mindspring.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
Danny writes:
 => All,
 => Mar 29 03:19:15 dsc_proto_1 kernel: XFS unmount got error 38 
 => Mar 29 03:19:15 dsc_proto_1 kernel: linvfs_put_super: vfsp/0xc3bc2ae0
 => left dangling! 
 => Mar 29 03:19:15 dsc_proto_1 kernel: VFS: Busy inodes after unmount.
 => Self-destruct in 5 seconds.  Have a nice day... 
 => Mar 29 03:19:56 dsc_proto_1 kernel: XFS: Filesystem has duplicate UUID -
 => can't mount 

 =>     Now: I'm pretty sure that a reboot would allow the mount to succeed; in
 => other words, /dev/md1 is still "mounted" in some way in the kernel;
 => hence the dup UUID.

If xfs_unmountfs doesn't get called, the uuid for the mounted xfs fs won't
get removed from the uuid table, and further mounts of that filesystem
will be rejected. There are a couple of paths in which the unmount can
fail to call xfs_unmountfs, but they shouldn't happen unless something
is really wrong anyway.

What I'm really curious about is why the unmount failed in the first
place - that definitely shouldn't be happening.

Can you give us some vitals on your setup? Are you using highmem, quota, 
acls, dmapi etc? Running any specific tests?

 =>     This machine is a test machine only.  Is there anything you'd like me
 => to try before I reboot?

I think it's too late now. If you can work out how to repeat this problem,
we should be able to suggest some ways to debug it.

Regards,
-----------------------------------------------------
 Daniel Moore                  dxm@xxxxxxx
 R&D Software Engineer         Phone: +61-3-98348209
 SGI Performance Tools Group   Fax:   +61-3-98132378
-----------------------------------------------------


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