| 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
| ||
|
Message-ID: <20140930231801.GB729@khazad-dum.debian.net> Date: Tue, 30 Sep 2014 20:18:01 -0300 From: Henrique de Moraes Holschuh <hmh@....eng.br> To: Pavel Machek <pavel@....cz> Cc: Theodore Ts'o <tytso@....edu>, kernel list <linux-kernel@...r.kernel.org>, jack@...e.cz, linux-ext4@...r.kernel.org, adilger.kernel@...ger.ca, Dmitry Monakhov <dmonakhov@...nvz.org> Subject: Re: ext4: 3.17? problems On Tue, 30 Sep 2014, Pavel Machek wrote: > > > So I had to hard power-down the machine. That should be perfectly > > > safe, as ext4 has a journal, and this is plain SATA disk, right? > > Yes, it should be safe. > > Good. ... > Is there some phase during shutdown where journalling no longer > protects fs integrity? Hmm... what kind of backing device? Because I have Crucial/Micron M500 SSDs here that _always_ complain (in a SMART counter/attribute) that they have been subject to a sudden poweroff *when subject to a normal system shutdown*. This is scaring me a great deal. Are we doing something different for SSDs in the scsi-sd or libata shutdown paths? -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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