| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 2 Oct 2006 02:50:05 -0400 From: Kyle Moffett <mrmacman_g4@....com> To: Gene Heskett <gene.heskett@...izon.net> Cc: linux-kernel@...r.kernel.org Subject: Re: ext3 corruption On Oct 01, 2006, at 23:24:48, Gene Heskett wrote: > On Sunday 01 October 2006 22:40, Molle Bestefich wrote: >> To reiterate: >> The distro halt script tries "umount -f" three times, which all >> fail with >> "Device or resource busy". > > Me too. > I'm getting those messages from the NFS stuff at shutdown time, > with NO NFS > shares active. I have had them for years. But the reboot goes on > eventually, and apparently without harm. What causes problems on _all_ of my softraid boxes is that without a whole bunch of pivot_root magic in the shutdown code to switch to a tmpfs and unmount my lvm-on-md-on-sata stuff, it's impossible to get the kernel to stop devices cleanly. I get all sorts of messages from the kernel about trying to stop MD devices and not being able to _after_ reboot is called, even though at that point it should just forcibly kill all userspace, unmount all filesystems, and deconstruct the MD/DM device tree. I see no reason why a successful shutdown or reboot call should _ever_ leave the disks in an inconsistent state. Cheers, Kyle Moffett - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists