linux-ext4 - [Bug 16019] Resume from hibernate corrupts ext4

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <201005211800.o4LI0U7U013111@demeter.kernel.org>
Date:	Fri, 21 May 2010 18:00:30 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 16019] Resume from hibernate corrupts ext4

https://bugzilla.kernel.org/show_bug.cgi?id=16019





--- Comment #7 from David Lowe <lowe@...wn.edu>  2010-05-21 18:00:27 ---
(In reply to comment #6)
> Just to test a theory, could you try doing "hdparm -W" on your disk(s) to check
> the write cache status?
> 
> If it's 1 (on), then prior to hibernate, can you try hdparm -W 0 on the disk(s)
> and see if the problem persists?  I'm wondering if it's possible that data in
> the drive's write cache got lost when the system powered down, if it wasn't
> properly flushed during hibernate.
> 
> You'll want to do hdparm -W 1 later to turn them back on if that was the
> original state.
> 
> Thanks,
> 
> -Eric

I gave that a try and did not find any difference.

The original state was 1 (on) so I set it to 0 and did a hibernate. 
The system comes back up with the unwritable disk as before.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html