From: Stan Hoeppner <stan@hardwarefreak.com>
To: Julien FERRERO <jferrero06@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS filesystem corruption
Date: Wed, 06 Mar 2013 21:56:03 -0600 [thread overview]
Message-ID: <51380FD3.5010302@hardwarefreak.com> (raw)
In-Reply-To: <CAPcwv6wZJSBtgF-L6KNSn6N6Y+wUZJFXdbcg+zYRwoaB2sDdjw@mail.gmail.com>
On 3/6/2013 9:08 AM, Julien FERRERO wrote:
> The filesystem was originally created with the command:
> # mkfs.xfs -f -l size=32m /dev/md0
It may be unrelated to your corruption, problem but I'm curious why you
are specifying a 32MB log section instead of letting mkfs.xfs make the
log size decision.
> corruption. I only know that units are used to be power cycle by
> operator while the fs is still mounted (no proper shutdown / reboot).
> My guess is the fs journal shall handle this case and avoid such
> corruption.
As others have stated, this operator needs to be flogged and educated.
A computer based video ingestion/playback system with disk storage and a
complex filesystem is not a tape deck. You can't can't simply power it
off as if it were a tape deck.
I would assume based on your description that this is a mobile storage
system, often moved from one location to another, probably in a van, and
this is why the operator simply hits the power switch? Live news crew
type application or similar?
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-07 3:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 15:08 XFS filesystem corruption Julien FERRERO
2013-03-06 15:15 ` Emmanuel Florac
2013-03-06 16:16 ` Julien FERRERO
2013-03-06 16:47 ` Ric Wheeler
2013-03-06 22:21 ` Emmanuel Florac
2013-03-06 23:12 ` Ric Wheeler
2013-03-07 13:15 ` Julien FERRERO
2013-03-07 13:40 ` Ric Wheeler
2013-03-07 23:22 ` Dave Chinner
2013-03-08 10:16 ` Julien FERRERO
2013-03-12 9:57 ` Martin Steigerwald
2013-03-08 8:39 ` Stan Hoeppner
2013-03-08 10:17 ` Julien FERRERO
2013-03-08 12:20 ` Ric Wheeler
2013-03-08 18:59 ` Stan Hoeppner
2013-03-09 9:11 ` Dave Chinner
2013-03-09 18:51 ` Stan Hoeppner
2013-03-10 22:45 ` Dave Chinner
2013-03-10 23:54 ` Stan Hoeppner
2013-03-11 0:50 ` Dave Chinner
2013-03-11 9:29 ` Stan Hoeppner
2013-03-11 22:45 ` Dave Chinner
2013-03-11 9:25 ` Julien FERRERO
2013-03-12 10:54 ` Emmanuel Florac
2013-03-12 10:42 ` Martin Steigerwald
2013-03-12 22:16 ` Stan Hoeppner
2013-03-07 3:56 ` Stan Hoeppner [this message]
2013-03-07 13:04 ` Julien FERRERO
2013-03-07 13:32 ` Stan Hoeppner
2013-03-10 2:50 ` Eric Sandeen
2013-03-10 22:11 ` Dave Chinner
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=51380FD3.5010302@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=jferrero06@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.