Re: Can't force unmount device
On 27/05/14 08:11, Andrei POPESCU wrote: On Lu, 26 mai 14, 10:15:40, Dr. Jennifer Nussbaum wrote: Also updatedb never seems to index the NSF-mounted files. There are also other indexers. KDE had one, but I forgot the name. Kind regards, Andrei Yes, I've seen a similar behaviour with gnome, where the indexer is tracker. This is on sid: $ aptitude why tracker i gnome Depends tracker-gui i A tracker-gui Depends tracker (= 1.0.1-2) -- Klaus -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53887467.6050...@gmail.com
Re: Can't force unmount device
On Lu, 26 mai 14, 10:15:40, Dr. Jennifer Nussbaum wrote: Also updatedb never seems to index the NSF-mounted files. There are also other indexers. KDE had one, but I forgot the name. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Can't force unmount device
I know this problem has been discussed endlessly online, but i cant get any of the suggestions to work. I have a Debian laptop that, when im at home, I mount via nfs to a local fileserver. Sometimes for no clear reason, i cant unmount it, and when this happens, i cant put the laptop to sleep. There's no swap on this drive, and it's not an encrypted filesystem. There are no symbolic links pointing to this device. I dont think anything is accessing the device, and I'm not in a directory on this disk, but nothing to figure this out works: $ sudo umount /mnt/RemoteDisk umount.nfs: /mnt/RemoteDisk: device is busy umount.nfs: /mnt/RemoteDisk: device is busy $ sudo umount -f /mnt/RemoteDisk umount.nfs: /mnt/RemoteDisk: device is busy umount.nfs: /mnt/RemoteDisk: device is busy $ So i try: $ sudo lsof | grep Remote This hangs, as does a simple lsof. So i try: $ sudo fuser -m /mnt/RemoteDisk This also hangs. So does: $ sudo fuser -u /mnt/RemoteDisk I end up having to power the computer down, which is extremely annoying. What could be causing this? Ive googled this up and down but still dont know what to try. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1401116541.87337.yahoomail...@web124503.mail.ne1.yahoo.com
Re: Can't force unmount device
Hi. On Mon, 26 May 2014 08:02:21 -0700 (PDT) Dr. Jennifer Nussbaum bg271...@yahoo.com wrote: I end up having to power the computer down, which is extremely annoying. Try 'unmount -l' for the offending filesystem. It is usually enough to fool suspend scripts into 'no nfs mounted, really' state. What could be causing this? Ive googled this up and down but still dont know what to try. What version of NFS are you using? Are you using 'hard' mount option (hint: don't). Did you tried 'intr' mount option? I've seen similar things for NFS4 with Kerberos authentication if client desynchronise with a server (~10 minutes of clock difference). Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140526193904.ee6c3b79abbef8701666a...@gmail.com
Re: Can't force unmount device
On Monday, May 26, 2014 11:39 AM, Reco recovery...@gmail.com wrote: Hi. On Mon, 26 May 2014 08:02:21 -0700 (PDT) Dr. Jennifer Nussbaum bg271...@yahoo.com wrote: I end up having to power the computer down, which is extremely annoying. Try 'unmount -l' for the offending filesystem. It is usually enough to fool suspend scripts into 'no nfs mounted, really' state. Wow, that did it! Thanks! What could be causing this? Ive googled this up and down but still dont know what to try. What version of NFS are you using? Are you using 'hard' mount option (hint: don't). Did you tried 'intr' mount option? I've seen similar things for NFS4 with Kerberos authentication if client desynchronise with a server (~10 minutes of clock difference). Not actually sure what version I'm using. I mount the share using: $ sudo mount -t nfs 192.168.1.5:/volume1/DiskStation /mnt/RemoteDisk Is there something else i should be doing? Is using umount -l a satisfactory way to solve this? Thank you! Jen -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1401119869.10652.yahoomail...@web124501.mail.ne1.yahoo.com
Re: Can't force unmount device
On Mon, 26 May 2014 08:57:49 -0700 (PDT) Not actually sure what version I'm using. I mount the share using: $ sudo mount -t nfs 192.168.1.5:/volume1/DiskStation /mnt/RemoteDisk That doesn't say much indeed. What about 'mount' output? It should show really long list of parameters for any NFS mount similar to: (rw,nosuid,nodev,relatime,vers=4.0,rsize=32768,wsize=32768,namlen=255,soft,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=foo,local_lock=none,addr=bar) Is there something else i should be doing? Is using umount -l a satisfactory way to solve this? Well, it's a hack. 'umount -l' doesn't really unmount filesystem for those processes who are using mountpoint in question. It's all other processes (including those who do suspend) are forced to believe that there's nothing mounted in there, move along. So, while 'umount -l' keeps NFS mount mounted, it: 1) Will unmount by itself once all processes who are holding it are gone. This may take awhile, of course. 2) This does not prevent you from mounting the same NFS share again into the same place. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140526202245.ff591f814aa0c1352ea88...@gmail.com
Re: Can't force unmount device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/26/2014 11:02 AM, Dr. Jennifer Nussbaum wrote: I know this problem has been discussed endlessly online, but i cant get any of the suggestions to work. I have a Debian laptop that, when im at home, I mount via nfs to a local fileserver. Sometimes for no clear reason, i cant unmount it, and when this happens, i cant put the laptop to sleep. There's no swap on this drive, and it's not an encrypted filesystem. There are no symbolic links pointing to this device. I dont think anything is accessing the device, and I'm not in a directory on this disk, but nothing to figure this out works: As confirmed elsewhere, lazy unmount gets this unmounted and lets you suspend the laptop. As far as the hangs themselves - first, I'd like to clarify something. You say you mount the laptop by NFS to a local fileserver. I'm not clear which direction you mean the mounting is done in. That is: Machine A has a NFS share defined. Machine B runs an appropriate NFS mount command, and gains access to files which are stored on machine A. Is the laptop machine A, or machine B? The former is what your phrasing (I ... mount [the laptop] via NFS to a local fileserver) leads me to expect, but the latter would be the more common scenario. Either way, I have an idea about what could be causing the hangs to occur, but the exact scenario would be different depending on the answer to that question. - -- The Wanderer Secrecy is the beginning of tyranny. A government exists to serve its citizens, not to control them. -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJTg2ybAAoJEASpNY00KDJrLPUQAKrZ0wcmKSH27KT3solxANV0 B5lrGchOQnMKbfKtd7tIcYJCYodIcLw7Ac5Me4HAupm7MIsauguHrIItkyUIPQhh QNNe1RUZ0rqGal8P31f/nxAetpoQ8yNU8JdJc0vVEA4joIR9VvvJi3z8u5cYzHla t70QDpSxhgLnTfr2d+XHwD2N9NL56xPspYS4nZMuGlxcs6hKrzTT6Rb4+qlLg3p2 VThhTmg7hrrop4hY19RwfosU/RGwt4x3NXd3sEF9ROa908+wP6hWG0pS7/nFwuBh rD5mtXehmcUUqywdRJgXRdqXMBHgHxa95xib/Alf09r8kca1NtBjEIz8F7H/R8kk GFiApv+eA6qpaMBlCP0+IrCOKQIOk9e9IjFb8Tog48BtnMrVSMduYilL51+bDAdY 87WYA+ArDMJznPyLjIDNi3b+uLqDlygtpK3NWWfnIixeQdnCMJqQyIm0BatjvJhx sAhwJJ7ddGjKNbIseyewW7wkX3jPcl3jffpkdreLWHKJI8YF+AbD4WukydgcrWXu EiHA8y5tknhpehJId76thQesMthUpNKJwvVZG72rmjAv3Gwm06XOIM4/oeTeRbat qdXevf8rr7GbUGpoWKc54g1zzQcQrsdug2gGGzHp2OlNO1iZZ0/GmJME7N1wDLTl fTJESG72wyr8QRtL/Vsb =3AUj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53836c9b.9000...@fastmail.fm
Re: Can't force unmount device
On Monday, May 26, 2014 12:32 PM, The Wanderer wande...@fastmail.fm wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/26/2014 11:02 AM, Dr. Jennifer Nussbaum wrote: I know this problem has been discussed endlessly online, but i cant get any of the suggestions to work. I have a Debian laptop that, when im at home, I mount via nfs to a local fileserver. Sometimes for no clear reason, i cant unmount it, and when this happens, i cant put the laptop to sleep. There's no swap on this drive, and it's not an encrypted filesystem. There are no symbolic links pointing to this device. I dont think anything is accessing the device, and I'm not in a directory on this disk, but nothing to figure this out works: As confirmed elsewhere, lazy unmount gets this unmounted and lets you suspend the laptop. As far as the hangs themselves - first, I'd like to clarify something. You say you mount the laptop by NFS to a local fileserver. I'm not clear which direction you mean the mounting is done in. That is: Machine A has a NFS share defined. Machine B runs an appropriate NFS mount command, and gains access to files which are stored on machine A. Is the laptop machine A, or machine B? The former is what your phrasing (I ... mount [the laptop] via NFS to a local fileserver) leads me to expect, but the latter would be the more common scenario. Yes, that's right. I have a fileserver at home that has an NFS share defined; this share is used by various machines on my home network, and by the laptop when i have the laptop at home. As said elsewhere in thread, i mount the share on the laptop by saying $ sudo mount -t nfs 192.168.1.5:/volume1/DiskStation /mnt/RemoteDisk where 192.168.1.5 is the address of the fileserver, and /volume1/DiskStation is the NFS share. When im leaving home and the laptop doesnt need access to this, i (try to) unmount the share so i can suspend the laptop and leave. Does that help? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1401122417.38531.yahoomail...@web124502.mail.ne1.yahoo.com
Re: Can't force unmount device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/26/2014 12:40 PM, Dr. Jennifer Nussbaum wrote: On Monday, May 26, 2014 12:32 PM, The Wanderer wande...@fastmail.fm wrote: As far as the hangs themselves - first, I'd like to clarify something. You say you mount the laptop by NFS to a local fileserver. I'm not clear which direction you mean the mounting is done in. That is: Machine A has a NFS share defined. Machine B runs an appropriate NFS mount command, and gains access to files which are stored on machine A. Is the laptop machine A, or machine B? The former is what your phrasing (I ... mount [the laptop] via NFS to a local fileserver) leads me to expect, but the latter would be the more common scenario. Yes, that's right. I have a fileserver at home that has an NFS share defined; this share is used by various machines on my home network, and by the laptop when i have the laptop at home. So the laptop is machine B, then? That fits with the sort of scenario I would have expected. It's just that I read mount [a machine] via NFS as mount a directory that's being shared by [a machine] over NFS, so I found the phrasing confusing. By any chance, when the suspend failure and NFS hang occurs, is there an 'updatedb' or 'updatedb.mlocate' process running on the laptop? updatedb normally runs once a day, by cron job, and scans all mounted filesystems for changes. It's supposed to ignore any filesystems of types listed in the PRUNEFS variable in /etc/updatedb.conf ; however, there appears to be a longstanding bug such that it does not in fact do this for (some?) NFS mounts. I can dig up one or more existing Debian bug reports for this if necessary. If the NFS filesystem is unavailable at the time when updatedb tries to access it - e.g. because the laptop has been suspended, taken out of range of the appropriate server, and woken back up - then updatedb will block waiting on the NFS access. (In theory it should resume automatically when the server becomes available again, but I don't know how reliable that behavior is.) When im leaving home and the laptop doesnt need access to this, i (try to) unmount the share so i can suspend the laptop and leave. If you always do unmount the share before taking the laptop off-network in this way, or if the problem sometimes occurs even when you did remember to unmount it, then I'm probably barking up the wrong tree. However, if you ever suspend the laptop with the NFS share mounted, then wake it up again while not connected to the appropriate network to talk to the fileserver, that could produce the behavior you're seeing. (The behavior could also occur if e.g. the laptop connects only wirelessly, and the wireless network connection drops during the time when updatedb wants to be scanning that filesystem. That's a less likely scenario, however.) - -- The Wanderer Secrecy is the beginning of tyranny. A government exists to serve its citizens, not to control them. -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJTg3NYAAoJEASpNY00KDJrcDMP+QF9SdFisuwLo8vMwc7SATOa BD4budzZk480t2mLyHFwAiK0ZWjIE0cwbkKcY966tM2PiZbN+4PzX/i2n8KFNqlx lZ1G7trWuX5fGa3cel0bpcbDdi+YUHjxlxVV6M6qrA9Ez8pSgp3RFyxAIVTpyFZR +3ERJ/f09BI1EK+NZpL1KRii6U2ht6MbLiZz10Mfc2J5i3ezUDzOrQymyRNOwqdA TdORQx8rYSwqXdfLMENWxZIqeRh4Kp/LsAPrWGZxFC2i+SX4J/SFV7AvePsDAOYT +0or1+1YxBe/+ihoWJRTSkw3U6lLIDXyBrYZKKAKppRxzS0hywfPA7obvZA2aMDQ M8j5XrI2VdcUvCTy6trPHjTptHQX+BAc9x3MfwNGasAadQVpIr5dXyORQ7rnDfQK lVKd3idU82njmPeU4Ay1wEylM5/GjvmJYKZuhE22IPArKV/xB8WKShc97cncXW9Z 8QzDDsQRJWK5JddEHL+55xLMJbwydfzvxgzVUV5gVKG95LC+eygKtgwOiU/rV0kF 0fHB4UAzjYpBRJIs6Bq2JeKhA0QDBWBYYBaLrmZmtXludGoDYIP5Yuf9TPO/JihS Dj0vFq8pcvckAipmd1FRDPpYsIGMjoVf3tAsFZGzzJlTnMIDcMFcVHWCwzz9Og3V yEaUBZ0NJO53Q8BDmDJm =WBuS -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53837358.3060...@fastmail.fm
Re: Can't force unmount device
On Monday, May 26, 2014 1:01 PM, The Wanderer wande...@fastmail.fm wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/26/2014 12:40 PM, Dr. Jennifer Nussbaum wrote: On Monday, May 26, 2014 12:32 PM, The Wanderer wande...@fastmail.fm wrote: As far as the hangs themselves - first, I'd like to clarify something. You say you mount the laptop by NFS to a local fileserver. I'm not clear which direction you mean the mounting is done in. That is: Machine A has a NFS share defined. Machine B runs an appropriate NFS mount command, and gains access to files which are stored on machine A. Is the laptop machine A, or machine B? The former is what your phrasing (I ... mount [the laptop] via NFS to a local fileserver) leads me to expect, but the latter would be the more common scenario. Yes, that's right. I have a fileserver at home that has an NFS share defined; this share is used by various machines on my home network, and by the laptop when i have the laptop at home. So the laptop is machine B, then? In your scheme, yes. That fits with the sort of scenario I would have expected. It's just that I read mount [a machine] via NFS as mount a directory that's being shared by [a machine] over NFS, so I found the phrasing confusing. Sorry, my unclearness. By any chance, when the suspend failure and NFS hang occurs, is there an 'updatedb' or 'updatedb.mlocate' process running on the laptop? No, i dont think so. This runs in the middle of the night and this is not when i remove the laptop. updatedb normally runs once a day, by cron job, and scans all mounted filesystems for changes. It's supposed to ignore any filesystems of types listed in the PRUNEFS variable in /etc/updatedb.conf ; however, there appears to be a longstanding bug such that it does not in fact do this for (some?) NFS mounts. I can dig up one or more existing Debian bug reports for this if necessary. Also updatedb never seems to index the NSF-mounted files. And nfs/NFS are listed in this conf file. When im leaving home and the laptop doesnt need access to this, i (try to) unmount the share so i can suspend the laptop and leave. If you always do unmount the share before taking the laptop off-network in this way, or if the problem sometimes occurs even when you did remember to unmount it, then I'm probably barking up the wrong tree. I dont always unmount the share; sometimes i forget. But the problem occurs even when i do try to unmount it, or rather i cant unmount the system as described in my first message. However, if you ever suspend the laptop with the NFS share mounted, then wake it up again while not connected to the appropriate network to talk to the fileserver, that could produce the behavior you're seeing. This does sometimes happen--i syspend the laptop, take it somewhere else, then it cant find the fileserver when it wakes up. How can i solve this? (Apart from just remembering to always unmount it before leaving home.) (The behavior could also occur if e.g. the laptop connects only wirelessly, and the wireless network connection drops during the time when updatedb wants to be scanning that filesystem. That's a less likely scenario, however.) I connect the laptop both wired and wifi, but as said above it doesnt seem to scan the filesystem using updatedb. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1401124540.89418.yahoomail...@web124506.mail.ne1.yahoo.com
Re: Can't force unmount device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/26/2014 01:15 PM, Dr. Jennifer Nussbaum wrote: On Monday, May 26, 2014 1:01 PM, The Wanderer wande...@fastmail.fm wrote: On 05/26/2014 12:40 PM, Dr. Jennifer Nussbaum wrote: Yes, that's right. I have a fileserver at home that has an NFS share defined; this share is used by various machines on my home network, and by the laptop when i have the laptop at home. By any chance, when the suspend failure and NFS hang occurs, is there an 'updatedb' or 'updatedb.mlocate' process running on the laptop? No, i dont think so. This runs in the middle of the night and this is not when i remove the laptop. I wouldn't have expected it to be a problem either, for that exact reason, but I've seen this issue repeatedly on my own laptop when I don't unmount an NFS share before leaving my home network to go to work. The updatedb cron job is supposed to run at 6:25 AM (I think), but in some cases I've seen it running at considerably later times. I haven't tracked down the reason, or if I have I've forgotten it. updatedb normally runs once a day, by cron job, and scans all mounted filesystems for changes. It's supposed to ignore any filesystems of types listed in the PRUNEFS variable in /etc/updatedb.conf ; however, there appears to be a longstanding bug such that it does not in fact do this for (some?) NFS mounts. I can dig up one or more existing Debian bug reports for this if necessary. Also updatedb never seems to index the NSF-mounted files. It's not supposed to, and of course if it can't access the filesystem it won't be able to. And nfs/NFS are listed in this conf file. Yes - as I said, there's a bug such that they get ignored even though they're listed there. When im leaving home and the laptop doesnt need access to this, i (try to) unmount the share so i can suspend the laptop and leave. If you always do unmount the share before taking the laptop off-network in this way, or if the problem sometimes occurs even when you did remember to unmount it, then I'm probably barking up the wrong tree. I dont always unmount the share; sometimes i forget. But the problem occurs even when i do try to unmount it, or rather i cant unmount the system as described in my first message. I apologize, I was unclear. By the time you attempt a suspend that will fail, I would expect the updatedb process to already be hung, from a *previous* (probably successful) suspend attempt where the unmount did not get run. The scenario I'm envisioning is: * You mount the NFS share. * You suspend successfully, without unmounting the share. * You leave the network where the fileserver is. * You wake up the laptop. * updatedb starts trying to scan the NFS share. * You attempt to suspend, or to unmount the share, and fail. I've seen that exact scenario repeatedly in my own use. However, now that I look at it more closely, it doesn't seem like an exact match for what you've described; for one thing, it would mean you'd be seeing the failure when suspending while away from home, rather than when suspending to leave home. However, if you ever suspend the laptop with the NFS share mounted, then wake it up again while not connected to the appropriate network to talk to the fileserver, that could produce the behavior you're seeing. This does sometimes happen--i syspend the laptop, take it somewhere else, then it cant find the fileserver when it wakes up. How can i solve this? (Apart from just remembering to always unmount it before leaving home.) Depends what you mean by solve. To let the suspend succeed when the process is already hung, you should be able to just kill the 'updatedb.mlocate' process. You'll have to run the kill command as root, and you may well need the exact PID rather than being able to use 'pkill' or 'killall' to kill it by name. To prevent the updatedb hang from happening, you have to prevent updatedb from trying to scan the detached NFS mount. One way to do that is to always unmount the filesystem before suspending, but as you've noted, there's no guarantee you'll always remember to do that. Another way would be to remove the updatedb cron job entirely, so that it doesn't run at all. That seems like drastic overkill if you ever actually use the locate command, but it would get the job done. Another way would be to get the PRUNEFS bug fixed. That would be the best option; if you choose to pursue it, good luck. - -- The Wanderer Secrecy is the beginning of tyranny. A government exists to serve its citizens, not to control them. -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJTg3uOAAoJEASpNY00KDJrI+MQAKelICbM5fAZcx0vkEGBfU5Z XCSGHO80MtwqbBDxuPfvoGFV6l+sexBBethSskoSt7hORVDMBrX7CNSmuUFQWsqY hIoSJ72IFLzRGTGftMjlPZ8ga1WFS/2+yK927uvnvltZCOQhOy1L4JLsF9anSwu5 2ph5UvqR+8p0cwKw1Vg9HULWzVwGuv9qg0rJZ8cLeIknwhkZHHcWgMq3lLRXxtyy
