From: Tejun Heo <htejun@gmail.com>
To: dusty@gmx.li
Cc: linux-ide@vger.kernel.org
Subject: Re: libata pm
Date: Thu, 31 Jan 2008 10:13:56 +0900 [thread overview]
Message-ID: <47A120D4.7030504@gmail.com> (raw)
In-Reply-To: <50028.82.140.53.128.1201728857.squirrel@ssl.cavemail.org>
dusty@gmx.li wrote:
> Sorry for my late answer, but i had to sort this out first.
> After replacing the first PSU with a new Corsair 650W the power no longer
> fluctuated more than 0,01 V (and this only when booting up the drives...)
> I did a full resync on both raid arrays and got no more errors or resets,
> but there were some inconsitencies during sync and the xfs filesystem on
> both arrays had to be repaired. Are these problems caused by the pm resets
> ?
libata EH won't lose any data as long as the hardware doesn't. If power
fluctuates causing your drive to briefly power down - this does happen
and you can hear the drive doing emergency unload when it happens, the
data in write buffer can be lost. On coming back, all that libata can
know is that the PHY suffered brief connection loss, so it resets the
device and goes on, so the data in the cache is lost now. It's
basically pulling the power plug from the harddrive while write is going
on and connecting it back quickly. You're bound to lose data.
--
tejun
next prev parent reply other threads:[~2008-01-31 1:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 18:03 libata pm dusty
2008-01-26 20:05 ` dusty
2008-01-26 23:33 ` Tejun Heo
2008-01-27 1:38 ` dusty
2008-01-27 19:34 ` dusty
2008-01-28 1:17 ` Tejun Heo
2008-01-28 10:31 ` dusty
2008-01-28 12:03 ` Tejun Heo
2008-01-30 21:34 ` dusty
2008-01-31 1:13 ` Tejun Heo [this message]
2008-02-01 13:42 ` dusty
2008-02-01 13:53 ` Tejun Heo
2008-02-01 14:06 ` Mark Lord
2008-02-01 15:05 ` Tejun Heo
2008-02-05 18:50 ` dusty
2008-02-01 15:12 ` dusty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47A120D4.7030504@gmail.com \
--to=htejun@gmail.com \
--cc=dusty@gmx.li \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).