Bug#490924: udev-udeb: Errors due to RO file system
tags 490924 pending thanks For people reading along on d-boot and seeing this BR for the first time: I noticed some errors from udev when aborting an installation. Turns out we need to stop udevd before unmounting file systems to prevent those. I've committed minor changes in both rootskel and finish-install that do just that. Tested lightly, but seems to work. On Tuesday 15 July 2008, Frans Pop wrote: > On Tuesday 15 July 2008, Marco d'Itri wrote: > > On Jul 15, Frans Pop <[EMAIL PROTECTED]> wrote: > > > Sending SIGTERM to all processes > > > udevd-event: delete_path: rmdir(/dev/.udev/names/vcs3) failed: > > > Read-only file system > > > > And why is /dev read only at this point? Is it even still mounted? > > Hmm. May well be no longer mounted. The error was what confused me a > bit, especially as there was an issue with RO mounts for normal > systems. > > Looks like we're doing: > /bin/umount -a -r > /sbin/swapoff -a > reboot > > So I guess we just need to stop udev cleanly before the umount. > What would be the best command for that? Just 'kill -15 $(pidof > udevd)'? signature.asc Description: This is a digitally signed message part.
Bug#490924: udev-udeb: Errors due to RO file system
reassign 490924 rootskel 1.63 retitle 490924 Should stop udevd before umount -a on shutdown thanks On Tuesday 15 July 2008, Marco d'Itri wrote: > On Jul 15, Frans Pop <[EMAIL PROTECTED]> wrote: > > Sending SIGTERM to all processes > > udevd-event: delete_path: rmdir(/dev/.udev/names/vcs3) failed: > > Read-only file system > > And why is /dev read only at this point? Is it even still mounted? Hmm. May well be no longer mounted. The error was what confused me a bit, especially as there was an issue with RO mounts for normal systems. Looks like we're doing: /bin/umount -a -r /sbin/swapoff -a reboot So I guess we just need to stop udev cleanly before the umount. What would be the best command for that? Just 'kill -15 $(pidof udevd)'? Just tried that and seems to work. Reassigning to rootskel as that's where the responsible script lives, but I'd appreciate your reaction if the above is correct. I also do wonder a bit what's changed that causes this with the new version of udev. I'm quite sure we did not see it with the old one. Thanks, Frans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#490924: udev-udeb: Errors due to RO file system
On Jul 15, Frans Pop <[EMAIL PROTECTED]> wrote: > Sending SIGTERM to all processes > udevd-event: delete_path: rmdir(/dev/.udev/names/vcs3) failed: Read-only file > system And why is /dev read only at this point? Is it even still mounted? -- ciao, Marco signature.asc Description: Digital signature
Bug#490924: udev-udeb: Errors due to RO file system
Package: udev-udeb Version: 0.124-1 If I abort an installation (using D-I), I get the following errors on the console: Sending SIGTERM to all processes udevd-event: delete_path: rmdir(/dev/.udev/names/vcs3) failed: Read-only file system udevd-event: unlink-secure: chown(/dev/vcs3, 0, 0) failed: Read-only file system udevd-event: unlink-secure: chmod(/dev/vcs3, ) failed: Read-only file system udevd-event: unlink-secure: unlink(/dev/vcs3) failed: Read-only file system Sending SIGKILL to all processes Note: I assume the same errors would be displayed at the end of a successfull install, but I just did not do any tests that far. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
