[opensuse] Self-destruct in 5 seconds. Have a nice day...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Huh? I notice the above in the warning log, with a bit more detail in the messages log: <1.5> 2019-10-28T22:50:42.623834+01:00 Isengard RPM - - install paprefs-lang-0.9.10-lp151.2.3.noarch: success <1.5> 2019-10-28T22:50:42.626233+01:00 Isengard RPM - - install paprefs-lang-0.9.10-lp151.2.3.noarch: success <1.5> 2019-10-28T22:50:42.626740+01:00 Isengard RPM - - Transaction ID 5db762b2 finished: 0 <3.6> 2019-10-28T22:55:58.063198+01:00 Isengard systemd 1 - - Unmounting /var/cache/zypp/nfs_packages... <0.4> 2019-10-28T22:55:58.093851+01:00 Isengard kernel - - - [194307.441511] VFS: Busy inodes after unmount of 0:54. Self-destruct in 5 seconds. Have a nice day... <3.6> 2019-10-28T22:55:58.149233+01:00 Isengard systemd 1 - - Unmounted /var/cache/zypp/nfs_packages. <4.5> 2019-10-28T22:59:38.383442+01:00 Isengard sudo - - - cer : TTY=pts/9 ; PWD=/home/cer ; USER=root ; COMMAND=/usr/sbin/iotop -o -d 3.3333 It may refer to the automated umounting of "/var/cache/zypp/nfs_packages", via nfs - fstab: telcontar.valinor:/data/storage_c/repositorios_zypp/ /var/cache/zypp/nfs_packages nfs noauto,nofail,x-systemd.automount,x-systemd.idle-timeout=300,_netdev,nfsvers=4 0 0 I see no message in the server at that timeframe. What does it mean? What will selfdestruct, my computer? :-o - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbdm6Rwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV6tEAn1fWIH/RaltA1eXYvzJs TJ5eGjUfAJ9D52D2G9RnlqPS9Xk4jMKX5/oeww== =/qsB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
[194307.441511] VFS: Busy inodes after unmount of 0:54. Self-destruct in 5 seconds. Have a nice day... [snip]
I see no message in the server at that timeframe. What does it mean? What will selfdestruct, my computer? :-o
Maybe the message says it quite clearly - vfs inodes were busy, but the real ones disappeared. Why that would happen, I don't know. Try googling "VFS: Busy inodes after unmount", plenty of hits, some going back 10-15 years. No obvious explanation though. -- Per Jessen, Zürich (8.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Oct 29, 2019 at 07:14:20AM +0100, Per Jessen wrote:
Carlos E. R. wrote:
[194307.441511] VFS: Busy inodes after unmount of 0:54. Self-destruct in 5 seconds. Have a nice day... [snip]
I see no message in the server at that timeframe. What does it mean? What will selfdestruct, my computer? :-o
Maybe the message says it quite clearly - vfs inodes were busy, but the real ones disappeared. Why that would happen, I don't know.
Try googling "VFS: Busy inodes after unmount", plenty of hits, some going back 10-15 years. No obvious explanation though.
This is actually a NFS bug in the 15.0 and 15.1 kernel happening during NFS umount. A 15.0 fix kernel update was released on Sunday, 15.1 is still waiting for submission. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Marcus Meissner wrote:
On Tue, Oct 29, 2019 at 07:14:20AM +0100, Per Jessen wrote:
Carlos E. R. wrote:
[194307.441511] VFS: Busy inodes after unmount of 0:54. [Self-destruct in 5 seconds. Have a nice day... [snip]
I see no message in the server at that timeframe. What does it mean? What will selfdestruct, my computer? :-o
Maybe the message says it quite clearly - vfs inodes were busy, but the real ones disappeared. Why that would happen, I don't know.
Try googling "VFS: Busy inodes after unmount", plenty of hits, some going back 10-15 years. No obvious explanation though.
This is actually a NFS bug in the 15.0 and 15.1 kernel happening during NFS umount.
A 15.0 fix kernel update was released on Sunday, 15.1 is still waiting for submission.
Wow, that surprises me, we use quite a bit of NFS, with 15.0 and 15.1. Thanks for the update. -- Per Jessen, Zürich (8.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Oct 29, 2019 at 9:45 AM Per Jessen <per@computer.org> wrote:
Try googling "VFS: Busy inodes after unmount", plenty of hits, some going back 10-15 years. No obvious explanation though.
This is actually a NFS bug in the 15.0 and 15.1 kernel happening during NFS umount.
A 15.0 fix kernel update was released on Sunday, 15.1 is still waiting for submission.
Wow, that surprises me, we use quite a bit of NFS, with 15.0 and 15.1.
Do you constantly mount and unmount them? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
On Tue, Oct 29, 2019 at 9:45 AM Per Jessen <per@computer.org> wrote:
Try googling "VFS: Busy inodes after unmount", plenty of hits, some going back 10-15 years. No obvious explanation though. This is actually a NFS bug in the 15.0 and 15.1 kernel happening during NFS umount.
A 15.0 fix kernel update was released on Sunday, 15.1 is still waiting for submission. Wow, that surprises me, we use quite a bit of NFS, with 15.0 and 15.1.
Do you constantly mount and unmount them?
Well, no. Only a couple of shares on auto-mount, the rest are permanent. /Per -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/10/2019 08.23, Andrei Borzenkov wrote:
On Tue, Oct 29, 2019 at 9:45 AM Per Jessen <per@computer.org> wrote:
Try googling "VFS: Busy inodes after unmount", plenty of hits, some going back 10-15 years. No obvious explanation though.
This is actually a NFS bug in the 15.0 and 15.1 kernel happening during NFS umount.
A 15.0 fix kernel update was released on Sunday, 15.1 is still waiting for submission.
Wow, that surprises me, we use quite a bit of NFS, with 15.0 and 15.1.
Do you constantly mount and unmount them?
Me, everytime I install something, except on the main machine The machine has just been upgraded to 15.1. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbgYtgAKCRC1MxgcbY1H 1S4LAJ9mhVVMdiWywJOoIZiREQ4ZY87D3wCdGbzy8LpfbUW7gbPSmFn7la6JzjM= =/+1c -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/10/2019 07.17, Marcus Meissner wrote:
On Tue, Oct 29, 2019 at 07:14:20AM +0100, Per Jessen wrote:
Carlos E. R. wrote:
[194307.441511] VFS: Busy inodes after unmount of 0:54. Self-destruct in 5 seconds. Have a nice day... [snip]
I see no message in the server at that timeframe. What does it mean? What will selfdestruct, my computer? :-o
Maybe the message says it quite clearly - vfs inodes were busy, but the real ones disappeared. Why that would happen, I don't know.
Try googling "VFS: Busy inodes after unmount", plenty of hits, some going back 10-15 years. No obvious explanation though.
This is actually a NFS bug in the 15.0 and 15.1 kernel happening during NFS umount.
A 15.0 fix kernel update was released on Sunday, 15.1 is still waiting for submission.
Oh :-) The message is very scary! - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbgYWAAKCRC1MxgcbY1H 1UjhAJ9In5vAuKcyWE1M7yxbStwybXu2FwCfXskWSuMlwP/TVXfY26jQpDlD7vQ= =9Sid -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/10/2019 07.14, Per Jessen wrote:
Carlos E. R. wrote:
[194307.441511] VFS: Busy inodes after unmount of 0:54. Self-destruct in 5 seconds. Have a nice day... [snip]
I see no message in the server at that timeframe. What does it mean? What will selfdestruct, my computer? :-o
Maybe the message says it quite clearly - vfs inodes were busy, but the real ones disappeared. Why that would happen, I don't know.
Try googling "VFS: Busy inodes after unmount", plenty of hits, some going back 10-15 years. No obvious explanation though.
I did google, some references to NFS and the filesystem being dead or that the machine would crash instantly. I mounted the filesystem and noticed no issue, and certainly did not crash. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbgX+wAKCRC1MxgcbY1H 1cFWAJ9bmprCsYZET8e8XwHJe/eLniffLgCfSX78oLPXCjaJI82Te6SfNgq12EY= =/Q02 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-10-28 06:08 PM, Carlos E. R. wrote:
What does it mean? What will selfdestruct, my computer? :-o
https://www.youtube.com/watch?v=MA2KmJMKFrQ ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/10/2019 15.09, James Knott wrote:
On 2019-10-28 06:08 PM, Carlos E. R. wrote:
What does it mean? What will selfdestruct, my computer? :-o
Yeah, I thought on those lines as well. Some very peculiar programmer humour. Spooky. Hey, but they do not assure the tape did destruct! Only the drive did. And Leonard Nimoy was there! Funny seeing him not as Spock ;-) - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXbhNQAAKCRC1MxgcbY1H 1RUQAJ4+SYHznKUbu8GXYH/6dS+MrqR6/wCeKlrJcf2WUi/vemKJq1vekNF6DBc= =I0R0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
James Knott -
Marcus Meissner -
Per Jessen