[Top] [All Lists]

Re: xfsdump INTERRUPT issue

To: stan@xxxxxxxxxxxxxxxxx
Subject: Re: xfsdump INTERRUPT issue
From: Jeffrey <grndlvl@xxxxxxxxx>
Date: Sat, 22 Dec 2012 11:10:24 -0500
Cc: "david@xxxxxxxxxxxxx >> Dave Chinner" <david@xxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=dHfXPPNRuIxxcw6vXZFWVTNz31WxOYhft5vanat/RAY=; b=UbA2EI61XQQBfIzUIW4vJwgrmQcUGt2XA3eZZYvVgDIzR7LZ9/mxxbjVgSLYi0Ga6v yFBWPZj0f2BqEUqohwo+L91hvqEr7ndNak3p/NO3XxYSaZYgrE8Rwv2/NXMPd6vzpP0T zj+i2Nm1y47zusMu7k1splfxKsNj0DjIVj1BsjsQmLYr6+T/xH3nD47L9OmPVq95l9M0 D/kzMiQCHUIeS9ibCOUI4aeRvxCV0MAGnbyVDZsbv7OVfkD6nKexrjob1VUJ4tG0rIfZ ru3xA6U/pz7PdQs+jES60gNII9nfdaskooXwHpZGwnrEKypAb1P1uvXp4lKSaBOE+xRX 3UpQ==
In-reply-to: <50D57382.2060900@xxxxxxxxxxxxxxxxx>
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> <50D57382.2060900@xxxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
Ok, I tried running the command. Here's my output:

# xfs_repair -n -r /dev/sda2 /dev/sda3
# Phase 1 - find and verify superblock...
# bad primary superblock - bad magic number 111
# attempting to find secondary superblock...
# ................

and the dots are still just going after about 15 min.

What should I do?


On 12/22/2012 03:46 AM, Stan Hoeppner wrote:
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.

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