From: Kevin Richter <xfs@pzystorm.de>
Cc: xfs@oss.sgi.com
Subject: Re: Problem with XFS on USB 2TB HD
Date: Thu, 13 Jan 2011 00:37:28 +0100 [thread overview]
Message-ID: <4D2E3B38.6010506@pzystorm.de> (raw)
In-Reply-To: <20101220105547.4f9e7218@galadriel.home>
> That's because you had the misfortune of garbling the root directory
> inode along with the superblock. That's a very specific corruption,
> but if the corruption occurred a few blocks away in a data extent
> you wouldn't even know about it until you restore from backup and
> realised the file content in the backup are corrupted. Indeed - you
> should consider that entire backup as corrupted and redo it from
> scratch.
I am wondering if there is a simple solution to backup/restore the inode
table (the relation "inode <-> filename").
With "ls -aliR" I get a list which I am now saving every few days.
The parameter "-i" displays the inode, that I can reconstruct the
filename from the inode, if this garbling error occurs a second time.
The reconstruction process probably would be a simple "grep | cut" thing.
Is there perhaps a finished script doing exactly this? Or any other ideas?
Bye,
Kevin
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-12 23:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 11:26 Problem with XFS on USB 2TB HD Kevin Richter
2010-12-19 2:04 ` Kevin Richter
2010-12-19 2:37 ` Stan Hoeppner
2010-12-19 14:57 ` Emmanuel Florac
2010-12-19 17:30 ` Eric Sandeen
2010-12-20 0:10 ` Dave Chinner
2010-12-20 2:56 ` Kevin Richter
2010-12-20 4:51 ` Dave Chinner
2010-12-20 9:55 ` Emmanuel Florac
2011-01-12 23:37 ` Kevin Richter [this message]
2011-01-13 13:15 ` Extreme fragmentation when backing up via NFS Phil Karn
2011-01-14 4:51 ` Dave Chinner
2011-01-13 21:52 ` Problem with XFS on USB 2TB HD Geoffrey Wehrman
2010-12-20 8:59 ` Michael Monnerie
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=4D2E3B38.6010506@pzystorm.de \
--to=xfs@pzystorm.de \
--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.