xfs
[Top] [All Lists]

Re: xfsdump INTERRUPT issue

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: xfsdump INTERRUPT issue
From: Jeffrey <grndlvl@xxxxxxxxx>
Date: Sun, 23 Dec 2012 08:42:35 -0500
Cc: stan@xxxxxxxxxxxxxxxxx, "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; bh=hKTJtrLMLjPOtdyQpwRHWc33zlhMp6Arpw9UMt02Eck=; b=tUoloxhR72Z/9k7bU9Qz/K9dOg6PMzj2vf3LV2MPz8HLJIHBDy2rOOzPingbHspSaO 2g2O7r0iMHhDblqR7tEpk1/tkx6+mHkyxjzO+MSrBfrGAfAeZopfn+r5jCbp6OjhVVPa LP2lPG3lH4mFJ6ZJZTeyxAGGOSJge2dEN2EBPta/Dh4oeV3rS3BZpb43+OSf3Q47/ybH 7Vk4+U9ftPee4Y6HT7B6eKn6vy0CIX0objcxXwZ/OLWn/iJyK3JBRjpNQsKqYb8v6ds6 7HZsHX6ZyGvNMsJJsMpayMWXSEu7uA9T6KKcjOQoGMhDXXQ553WnMbFE5jKIqHZ4LpEM /nBA==
In-reply-to: <20121222234532.GH15182@dastard>
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> <50D5DB70.3020308@xxxxxxxxx> <20121222234532.GH15182@dastard>
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
Here's my output:

# xfs_repair -n -r /dev/sda3 /dev/sda2
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 1
        - agno = 3
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 0
        - agno = 12
        - agno = 13
        - agno = 14
        - agno = 15
        - agno = 4
        - agno = 2
        - agno = 10
        - agno = 11
        - agno = 9
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

Best,
J.


On 12/22/2012 06:45 PM, Dave Chinner wrote:
On Sat, Dec 22, 2012 at 11:10:24AM -0500, Jeffrey wrote:
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?
Try pointing xfs_repair to the correct devices. From looking atthe
earlier xfs_info output you posted, you've told it the
realtime device is the data device and vice versa. i.e. you should
be running:

# xfs_repair -n -r /dev/sda3 /dev/sda2


Cheers,

Dave.

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