[Top] [All Lists]

Re: xfsdump INTERRUPT issue

To: Jeffrey Ellis <jellis@xxxxxxxx>
Subject: Re: xfsdump INTERRUPT issue
From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Date: Sat, 22 Dec 2012 02:46:58 -0600
Cc: "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <9AF752E5-941B-491F-A7DE-5D978DFFB3B0@xxxxxxxx>
References: <50D2A038.2040501@xxxxxxxxxxxxxxxxx> <CCF8A128.B0C13%jellis@xxxxxxxx> <20121221032026.GD15182@dastard> <FBB37644-0ED3-446B-BAAA-92E1389BB9DC@xxxxxxxx> <50D49899.2090901@xxxxxxxxxxxxxxxxx> <9AF752E5-941B-491F-A7DE-5D978DFFB3B0@xxxxxxxx>
Reply-to: stan@xxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
On 12/21/2012 4:06 PM, Jeffrey Ellis wrote:
> Sorry, don't you want me to perform the repair and then try the restore 
> again? If I use -n seems like that wouldn't actually repair the volume?

It's called a "dry run" Jeffrey.  It will tell you what problems it
finds but without attempting to fix them.  Sometimes it's better to see
what is broken and in what way BEFORE actually attempting to fix it, as
the fixes may sometimes include unintended consequences.

What we're doing here is looking both ways twice before crossing the
street, instead of stepping into traffic without looking.

So my advice is to run with "-n" and post the output of the command so
we (mostly Dave) can see what's wrong before you actually make the
repairs.  He may tell you to go ahead and run the destructive repair, or
depending on what he sees he may have you perform some other tasks
before that.

You had no experience with XFS before embarking on this DVR drive
migration, and little to no experience with *nix.  You are unable to
digest the information in the man pages, stumbling with the commands we
give you, etc.  Thus it makes a lot of sense to play it safe with
everything you do here.


> On Dec 21, 2012, at 12:12 PM, Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx> wrote:
>> On 12/21/2012 9:32 AM, Jeffrey Ellis wrote:
>>> xfs_repair /dev/sda2
>>> xfs_repair: /dev/sda2 contains a mounted filesystem 
>>> xfs_repair /dev/sda3
>>> xfs_repair: cannot open /dev/sda3: Device or resource busy
>> ~$ man xfs_repair
>> ... the filesystem to be repaired must be unmounted ...
>> Note the "-r" option and the "-n" option.  The former specifies the
>> realtime device (partition) and the latter allows you to do a non
>> destructive repair, i.e. a "check", on a mounted filesystem.  Probably a
>> good idea at this point.    
>> So you might try something like:
>> ~$ xfs_repair -n -r /dev/sda2 /dev/sda3
>> -- 
>> Stan
>> _______________________________________________
>> xfs mailing list
>> xfs@xxxxxxxxxxx
>> http://oss.sgi.com/mailman/listinfo/xfs
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs

<Prev in Thread] Current Thread [Next in Thread>