xfs
[Top] [All Lists]

Re: XFS filesystem claims to be mounted after a disconnect

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: XFS filesystem claims to be mounted after a disconnect
From: Martin Papik <mp6058@xxxxxxxxx>
Date: Mon, 02 Jun 2014 14:22:15 +0300
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=fW8bCTCWhc0zPLMzcMoS0/M61XAsyYgsHh3kuZS2+RI=; b=alfQEx7gdwG44ilG06NbGD1K27sZKcjhITvMG5L3eblc4ZyMnekNAOHy7p+c+l/NZW JNaGG9X3cUnmsImH4iJ3CGdTygWOHzbQhCuInbDEeGQVKD9NJtGkPGYDzaNRg17ZyeX2 +uTQE2kieuWYYUhBufc9NjhAY4qqTpIl9e1f7Lra1b5i9x3KKtTWqtJHcstURmkS2Wrl nI6HPwUcSm9u2b7YzNZkov7bNaMnUzSAn/LsYYiI6ZhvndDDOuFz1NO0szt9fKaFgr0o ONHAr3PHAVmKXOSiiEE+1GjteHvn+irtCscvO4uSGSjlWxX2EMganuAmpeL6feXpSGxN Ry2g==
In-reply-to: <20140503030221.GJ26353@dastard>
References: <5363A1D8.2020402@xxxxxxxxx> <5363B4C9.4000900@xxxxxxxxxxx> <5363CB5E.3090008@xxxxxxxxx> <5363CD70.3000006@xxxxxxxxxxx> <5363DBD7.4060002@xxxxxxxxx> <5363E65C.6010006@xxxxxxxxxxx> <5363ECE8.6030706@xxxxxxxxx> <20140502233512.GE26353@dastard> <536432A0.6000405@xxxxxxxxx> <20140503030221.GJ26353@dastard>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


>> How can I detect this situation? I mean I didn't see anything in 
>> /proc/mounts or references to the mount point from /proc/<pid>/*,
>> so I only managed to correct it (chdir elsewhere) by chance on a
>> hunch. Would it not be desirable to know that there's a phantom
>> FS referenced by a number of processes?
> 
> lsof.

No good. It happened again and the only thing showing up in lsof
that's even remotely a match is the kernel process associated with the
filesystem instance. "[xfs-data/sde103]". The mountpoint has been
removed by the automatic mounting facility (udev? systemd?). The
device is no longer id /dev (udev?). There's nothing useful in the
output of "find /proc -ls" either.

Any other suggestions to locate the processes that are holding up XFS?

Martin

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJTjF5dAAoJELsEaSRwbVYrO7IP/016AVgVrdCQ2Vm95hFT5rdu
LH6Sz0mpnZn6mAliNLAa+wFpXArDb6VPyssmomzNLgnpA95qLcfJeBqs1wF88tiA
GO+aFSX3o3npAokbaq1N5c1dKz/g9lpsUPBkmiUEqcPLJMOKdJdSSd4T2nnnKrkD
uDGRmEPZGKXLt75Z0SajnG8oX22bSQdzREn2o4DXZy+RJF9G8wsc490b8TzijDul
AtL/2zlRL45LqbcaNNAOARUiTN4IAxy3xwYRU+xXKhqojPRc0x8K4wrjnGcsiw4x
Cz5HjJ6CdBLmjn69TRf+S5Y/UXtUcyFOIS0XIUwYg6KtwrI1BY+N+GpkSJNG/DcH
0lAN6n7UBTAADw54ZJdYhyw5aUt9OEXdDx2nIuTxq+X/6u4ydEDchJWPvyLG2nv9
Z2vObyh07X9n7h+zknK3yBxlHHNcpi1/d3njxRSa3GKQIPKNbrLNkrFqB4U4+isr
qrcldbcke5d6sUP/VdvjeOGTYWtymx8KqL1MDGPRXruOO1Y6N8DWTbseQCbeoQlS
k0L9md5FsZOPG/aUgXHvD4350sKqYpQk2pgoGW7Ia6F+5nwi1TdSd8R6mlGJ0GyW
hMymVeykhb19mVJzdc7UlmxyAUBUEd2zGEeO0uSenHt19yWc93vfEHG6GCtxFpu6
sxblWr9nRfPi6sOw7oUF
=xn+2
-----END PGP SIGNATURE-----

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