Re: [Bug 432237] Re: difficult to recover from filesystem errors
On Fri, 2009-10-09 at 16:28 +, Ernst Zlo wrote: With or without your ~beta5: kernel 2.6.31-12 will hang with a VBd in the /etc/fstab. Is the mountall.log of any interest for you, when the VBd is NOT mounted (which I am forced now, because otherwise my kernel won't work)? And afterwards I only can supply you with a mountall.log when I have unmounted the VBd again? I obviously need to see the log *with* the VBd in /etc/fstab of mountall failing, as it's the failure I need to diagnose. Scott -- Scott James Remnant sc...@ubuntu.com -- difficult to recover from filesystem errors https://bugs.launchpad.net/bugs/432237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 432237] Re: difficult to recover from filesystem errors
Am Samstag, den 10.10.2009, 10:41 + schrieb Scott James Remnant: On Fri, 2009-10-09 at 16:28 +, Ernst Zlo wrote: With or without your ~beta5: kernel 2.6.31-12 will hang with a VBd in the /etc/fstab. Is the mountall.log of any interest for you, when the VBd is NOT mounted (which I am forced now, because otherwise my kernel won't work)? And afterwards I only can supply you with a mountall.log when I have unmounted the VBd again? I obviously need to see the log *with* the VBd in /etc/fstab of mountall failing, as it's the failure I need to diagnose. And just this is impossible at the moment sigh I'll go and get me a daily snapshot to see, if it's better with that (this will last till monday, because I'm off now) Scott -- Scott James Remnant sc...@ubuntu.com -- difficult to recover from filesystem errors https://bugs.launchpad.net/bugs/432237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 432237] Re: difficult to recover from filesystem errors
On Fri, 2009-10-09 at 13:45 +, Dave Martin wrote: However, I still have a couple of issues: 1) A filesystem last mounted in future error is still treated as serious enough to interrupt the boot process and require interaction via mountall-shell. My view is that this is not appopriate because this may well happen when Windows fiddles with the clock on a dual-boot system, or when there's some other RTC problem. The filesystem upstream author disagrees unfortunately; which is why that error is there. Apparently the inconsistency causes problems for journalled filesystems. Now, you might say that this is one of those errors that fsck -a should fix automatically - but this issue has become a bit politically charged and the ext3/4 upstream is currently holding out having it a boot-critical error. At the same time, we have had bugs in the past with the system and hardware clock in Ubuntu being inconsistent - so we've wanted the hard error to collect the bug reports. For the Windows case - the hardware clock is in localtime, and our installer automatically sets that up when it detects the partition. The novice user may not have a good idea what to type in the maintenenace shell anyway. The problem will persist across boot until the system is sufficiently convinced to mount the fs read-write My suggestion would be that if the only apparent error with the root filesystem is that it was mounted in the future, boot should proceed, although a warning is appropriate. This appears to have been the Jaunty behaviour. Indeed, but sadly for the wrong reasons. You can get the jaunty behaviour by creating an /etc/e2fsck.conf file with the contents: [options] buggy_init_scripts = 1 (see what I mean about political? g) 2) If the mountall-shell exits with non-zero exit status, boot does not resume: init: mountall-shell main process (749) terminated with status 1 ...hang... This is unlikely to be appropriate: the default exit status of a shell is simply the exit status of the last command executed... which was not necessarily fsck. I believe fsck can exit with non-zero status for various non-fatal situations anyway? It's necessary to quit the shell with exit 0 to work around this... again, the novice user will have no clue about that. Good catch, I've committed a fix for that. Scott -- Scott James Remnant sc...@ubuntu.com -- difficult to recover from filesystem errors https://bugs.launchpad.net/bugs/432237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 432237] Re: difficult to recover from filesystem errors
On Fri, 2009-10-09 at 14:02 +, Ernst Zlo wrote: VirtualBox shared folder is to blame (which I mount in my /etc/fstab with the line extras /media/xtra vboxsf uid=1000,gid=1000,rw 0 0 stops the photon torpedos ;-) When I remove the line everything's smooth and perfect. I'd already fixed this one, and ~boot5 is uploading right now. Hope that one works out for you! Scott -- Scott James Remnant sc...@ubuntu.com -- difficult to recover from filesystem errors https://bugs.launchpad.net/bugs/432237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 432237] Re: difficult to recover from filesystem errors
On Fri, 2009-10-09 at 15:16 +, Ernst Zlo wrote: And by typing this essay of #...@!* bugs it becomes clear to me: please give me ~beta6 because without ~beta5 nothing goes, with ~beta5 nothing goes either. You haven't supplied your debug.log Scott -- Scott James Remnant sc...@ubuntu.com -- difficult to recover from filesystem errors https://bugs.launchpad.net/bugs/432237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 432237] Re: difficult to recover from filesystem errors
On Thu, 2009-10-08 at 11:17 +, Ernst Zlo wrote: I've installed your update: VirtualBox now hangs with the mounting of the shared folder. forever. Thanks. I've fixed this issue, new upload to the PPA is pending. Again, I would appreciate testing. Scott -- Scott James Remnant sc...@ubuntu.com -- difficult to recover from filesystem errors https://bugs.launchpad.net/bugs/432237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 432237] Re: difficult to recover from filesystem errors
On Thu, 2009-10-08 at 11:24 +, Dave Martin wrote: Before installing your update, running sudo mountall --debug on a booted system (this is mountall version 0.1.8) produces the attached output and appears to deadlock. The mountall process does not terminate. ** Attachment added: mountall.log http://launchpadlibrarian.net/33292692/mountall.log This log is not from the PPA, I'd prefer to see the log from the PPA. Scott -- Scott James Remnant sc...@ubuntu.com -- difficult to recover from filesystem errors https://bugs.launchpad.net/bugs/432237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 432237] Re: difficult to recover from filesystem errors
On Thu, 2009-10-08 at 11:53 +, Dave Martin wrote: By default, mountall throws a lot of Read-only filesystem errors while trying to clean /tmp, and drops to a root shell. Alternatively, if I remount the root filesystem read-write before running init, init (or possibly mountall) appears to deadlock; no messages appear, and the platform does not boot. I believe I have fixed this bug, new upload pending in the PPA - again I would appreciate testing. Scott -- Scott James Remnant sc...@ubuntu.com -- difficult to recover from filesystem errors https://bugs.launchpad.net/bugs/432237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 432237] Re: difficult to recover from filesystem errors
** Attachment added: mountall.log http://launchpadlibrarian.net/33292692/mountall.log This log is not from the PPA, I'd prefer to see the log from the PPA. Apologies... looks like I misunderstood your instructions there... [...] By default, mountall throws a lot of Read-only filesystem errors while trying to clean /tmp, and drops to a root shell. Alternatively, if I remount the root filesystem read-write before running init, init (or possibly mountall) appears to deadlock; no messages appear, and the platform does not boot. I believe I have fixed this bug, new upload pending in the PPA - again I would appreciate testing. OK... currently under way. I will take a short while since PPAs don't magically build for armel yet... -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- difficult to recover from filesystem errors https://bugs.launchpad.net/bugs/432237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 432237] Re: difficult to recover from filesystem errors
On Thu, 2009-10-08 at 15:14 +, Dave Martin wrote: By default, mountall throws a lot of Read-only filesystem errors while trying to clean /tmp, and drops to a root shell. Alternatively, if I remount the root filesystem read-write before running init, init (or possibly mountall) appears to deadlock; no messages appear, and the platform does not boot. I believe I have fixed this bug, new upload pending in the PPA - again I would appreciate testing. OK... currently under way. I will take a short while since PPAs don't magically build for armel yet... Still having issues, but I'll have those licked by tomorrow ;-) Scott -- Scott James Remnant sc...@ubuntu.com -- difficult to recover from filesystem errors https://bugs.launchpad.net/bugs/432237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
