| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Fwd: xfs - fixing wrong xfs size |
| From: | johahoff <jh@xxxxxxxxxxxxxxx> |
| Date: | Sun, 14 Nov 2010 03:16:01 -0800 (PST) |
| In-reply-to: | <4BE1EF9D.2030901@xxxxxxxxxxx> |
| References: | <dbd747120904130713t7388971axf75ee779b5b1e1f2@xxxxxxxxxxxxxx> <49E353FD.5060207@xxxxxxxxxxx> <dbd747120904130933i6ae66aedt7912a47b7e561f76@xxxxxxxxxxxxxx> <4BE1EF9D.2030901@xxxxxxxxxxx> |
> You can use xfs_db to set it; or you could comment out the kernel > check... and mount readonly, and copy off the data you can get to? I have got the same problem after recovering a xfs volume using ddrescue. It seems that the new 1 TB drive I dd'ed to is a few blocks short ... I had a look at the xfs_db man page, but wasn't able to figure out which command would allow me to set the block count of the fs. Can you please give the appropriate commands? I think I'll be able to figure out the correct counts on my own. Thanks a lot! -Johannes -- View this message in context: http://old.nabble.com/xfs---fixing-wrong-xfs-size-tp23023562p30211747.html Sent from the Xfs - General mailing list archive at Nabble.com. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_repair of critical volume, Dave Chinner |
|---|---|
| Next by Date: | Re: [PATCH] xfstests 246: Test for race between direct I/O and mmap, Lachlan McIlroy |
| Previous by Thread: | Re: xfs Digest, Vol 27, Issue 39, Eli Morris |
| Next by Thread: | Re: Fwd: xfs - fixing wrong xfs size, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |