xfs
[Top] [All Lists]

Re: xfsdump INTERRUPT issue

To: "stan@xxxxxxxxxxxxxxxxx" <stan@xxxxxxxxxxxxxxxxx>
Subject: Re: xfsdump INTERRUPT issue
From: Jeffrey Ellis <jellis@xxxxxxxx>
Date: Fri, 21 Dec 2012 17:06:39 -0500
Cc: "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <50D49899.2090901@xxxxxxxxxxxxxxxxx>
References: <50D2A038.2040501@xxxxxxxxxxxxxxxxx> <CCF8A128.B0C13%jellis@xxxxxxxx> <20121221032026.GD15182@dastard> <FBB37644-0ED3-446B-BAAA-92E1389BB9DC@xxxxxxxx> <50D49899.2090901@xxxxxxxxxxxxxxxxx>
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?

Best,
J. 

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

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