From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 16019] Resume from hibernate corrupts ext4
Date: Fri, 21 May 2010 18:00:30 GMT
Message-ID: <201005211800.o4LI0U7U013111@demeter.kernel.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
To: linux-ext4@vger.kernel.org
Return-path:
Received: from demeter.kernel.org ([140.211.167.39]:59578 "EHLO
demeter.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
with ESMTP id S1755733Ab0EUSAb (ORCPT
); Fri, 21 May 2010 14:00:31 -0400
Received: from demeter.kernel.org (localhost.localdomain [127.0.0.1])
by demeter.kernel.org (8.14.3/8.14.3) with ESMTP id o4LI0UM7013112
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for ; Fri, 21 May 2010 18:00:30 GMT
In-Reply-To:
Sender: linux-ext4-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=16019
--- Comment #7 from David Lowe 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.