| To: | Jeffrey <grndlvl@xxxxxxxxx> |
|---|---|
| Subject: | Re: xfsdump INTERRUPT issue |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Sun, 23 Dec 2012 10:45:32 +1100 |
| Cc: | stan@xxxxxxxxxxxxxxxxx, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| In-reply-to: | <50D5DB70.3020308@xxxxxxxxx> |
| 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> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfsdump INTERRUPT issue, Jeffrey |
|---|---|
| Next by Date: | Re: xfsdump INTERRUPT issue, Jeffrey Ellis |
| Previous by Thread: | Re: xfsdump INTERRUPT issue, Jeffrey |
| Next by Thread: | Re: xfsdump INTERRUPT issue, Jeffrey Ellis |
| Indexes: | [Date] [Thread] [Top] [All Lists] |