public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: "Passerone, Daniele" <Daniele.Passerone@empa.ch>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs data loss
Date: Fri, 28 Aug 2009 10:17:39 -0700	[thread overview]
Message-ID: <4A981133.6060009@sandeen.net> (raw)
In-Reply-To: <B9A7B002C7FAFC469D4229539E909760308DA65345@DU-EXC-MAIL.empa.emp-eaw.ch>

Passerone, Daniele wrote:
>>> Due to a power shock, suddenly and without log messages about one half
>> (5 TB) of the user
>>> directories on /dev/md4 have disappeared.
>> I presume you mean after a reboot?
> 
> 
> 
> No! No reboot at all.

Ok then perhaps I don't know what you mean by "power shock"

> The directories were mounted via nfs to all our cluster,
> and are of the type 
> 
> /pool/user
> 
> all directories from 
> 
> /pool/g*
> 
> to
> 
> /pool/z*
> 
> have disappeared.

On the server as well?  Or just clients?  -really- no server-side errors 
in the logs?

Are you sure the storage hardware & the md volume is in ok shape?

> Of course NO COMMAND of the kind rm /pool/[g-z]* was issued.
> 
>> Were the lost directories recently created?  I've never heard of
>> untouched, existing directories disappearing after a power loss...
>>
> 
> Not at all.
> Here I am.
>> Not much to go on here I'm afraid.  SLES10 is an old kernel, but it's
>> supported by SuSE at least.
>>
> 
> Can you use my metadata, or is it useless?

Not yet, still wondering what really happened.

-eric

> Thank you!
> 
> Daniele
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-08-28 17:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27  7:22 xfs data loss Passerone, Daniele
2009-08-27  9:41 ` Christian Kujau
2009-08-27  9:47   ` Passerone, Daniele
2009-08-27 10:09     ` Christian Kujau
2009-08-27  9:54   ` Passerone, Daniele
2009-08-28  4:16 ` Eric Sandeen
2009-08-28  9:19   ` Passerone, Daniele
2009-08-28 17:17     ` Eric Sandeen [this message]
2009-08-28 19:42       ` Passerone, Daniele
2009-08-29  6:08       ` Passerone, Daniele
2009-08-29  7:45         ` Ralf Gross
2009-08-29  7:11       ` Passerone, Daniele
2009-08-29 20:03       ` Passerone, Daniele
2009-08-29 22:14         ` Michael Monnerie
2009-08-29 22:52       ` Passerone, Daniele
2009-08-30  1:24         ` Eric Sandeen
2009-08-30  8:17           ` Michael Monnerie
2009-09-01 12:45         ` Peter Grandi
2009-09-01 22:16           ` Michael Monnerie
2009-09-04 11:08           ` Andi Kleen
2009-08-29 14:08 ` Peter Grandi
  -- strict thread matches above, loose matches on Subject: below --
2009-09-03 15:31 Passerone, Daniele
2009-09-05 18:29 ` Peter Grandi
     [not found]   ` <4AA3261E.1000005@sandeen.net>
2009-09-06 20:30     ` Peter Grandi
2009-09-04 11:45 Passerone, Daniele
2009-09-06  9:00 Passerone, Daniele
2009-09-06  9:30 ` Michael Monnerie
2009-09-06 21:00 ` 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=4A981133.6060009@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=Daniele.Passerone@empa.ch \
    --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