From: Eric Sandeen <sandeen@sandeen.net>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: adamantzj <tzj1983@163.com>,
Stan Hoeppner <stan@hardwarefreak.com>,
xfs@oss.sgi.com
Subject: Re: power failure causes files loss
Date: Sat, 24 Apr 2010 14:21:01 -0500 [thread overview]
Message-ID: <4BD3449D.9020802@sandeen.net> (raw)
In-Reply-To: <201004241905.44282.hpj@urpla.net>
Hans-Peter Jansen wrote:
> On Saturday 24 April 2010, 00:25:41 Stan Hoeppner wrote:
>> adamantzj put forth on 4/23/2010 6:28 AM:
>>> Hello,
>>>
>>> I’m writing data on a server in my company, but power cut
>>> suddenly. I had to restart the machine, then I found that many files in
>>> the working directory had been lost. I made some tries with xfs_repair
>>> and it didn't repair my corrupted file.
>>>
>>> What are the reasons caused this problem? I would like to know is what
>>> can I do to resolve this problem? Is XFS able to recover my file with
>>> its right content, at least a consistent content?
>>>
>>> I'm running a 2.6.24 kernel with xfsprogs-3.1.1, and the operating
>>> system is RedHat Enterprise Linux 5 Server (64-bit).
>>>
>>> Do you know if this problem has often been encountered, there is a
>>> way to proceed?
>>>
>>> Thank you !
>>>
>>> Adamant
>> XFS isn't the cause of your problem. Running without a proper UPS is the
>> cause of your problem. Fix the cause of your problem by purchasing a
>> properly sized and instrumented/monitored UPS. YOU CANNOT rely on your
>> OS or filesystem driver to prevent data loss due to power loss, or to
>> properly recover from such unexpected power loss if/when it occurs. This
>> is why you absolutely need to eliminate the possibility of unexpected
>> power loss. This is the sole purpose for the existence of companies such
>> as APC, Liebert, TrippLite and others.
>>
>> I'd have thought by 2010 that the entire IT cadre worldwide would already
>> be educated on proper power backup planning and procedures. I guess not.
>>
>> Acquire a proper UPS and configure it properly, specifically meaning
>> monitoring and alerts which will allow for performing a proper shutdown
>> during an extended outage, and your problems will disappear.
>
> While you're right for the general case of course, there are many other
> failure conditions, that an UPS will not prevent, eg. kernel crashes.
> Therefore there is an vivid interest, that any storage based filesystems
> should stay consistent _any_ time (and usually filesystem developers spend
> an considerable amount of their time on fixing such problems, if they
> arise).
>
> Adamant, the people reading here are rarely trained in telepathic
> capabilities. If you need more specific answers, you need to provide more
> specific details, eg. mount options, error logs, etc.
>
> Pete
See also:
"Eat My Data: How Everybody Gets File IO Wrong"
http://www.flamingspork.com/talks/
:)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-24 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 11:28 power failure causes files loss adamantzj
2010-04-23 20:40 ` Eric Sandeen
2010-04-23 22:25 ` Stan Hoeppner
2010-04-24 17:05 ` Hans-Peter Jansen
2010-04-24 19:21 ` Eric Sandeen [this message]
2010-04-24 21:12 ` Emmanuel Florac
2010-04-25 9:43 ` Peter Grandi
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=4BD3449D.9020802@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hpj@urpla.net \
--cc=stan@hardwarefreak.com \
--cc=tzj1983@163.com \
--cc=xfs@oss.sgi.com \
/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