| To: | Spam Magnet <spam.wax@xxxxxxxxx> |
|---|---|
| Subject: | Re: XFS: SB validate failed |
| From: | Stefan Smietanowski <stesmi@xxxxxxxxxx> |
| Date: | Fri, 30 May 2008 00:25:45 +0200 |
| Cc: | Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <3607657a0805291446t79808c63l664780c1cbc3d871@mail.gmail.com> |
| References: | <3607657a0805291005k457791cej1c5f867da0f95965@mail.gmail.com> <483EE5BD.8020407@sandeen.net> <3607657a0805291255i59fd006fi9d6836cf528d19a6@mail.gmail.com> <483F0BC3.2050901@sandeen.net> <3607657a0805291400h3c50165lea6fbea919deed0f@mail.gmail.com> <483F1AED.3010808@sandeen.net> <3607657a0805291446t79808c63l664780c1cbc3d871@mail.gmail.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.14 (Windows/20080421) |
Hi! Spam Magnet wrote: So I guess it doesn't matter if I do the image either using dd or xfsdump. I'd prefer dd since I get a lot of issues trying to compile xfsprogs under Irix.
$ mount -t xfs -o loop,ro disk.img /mnt But that's just a precaution and not necessary. This way if you manage to mess something up some way you can just try again since you're then mounting readonly. Unless you were planning on updating the image and then dd'ing it back to the original device of course. // Stefan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS: SB validate failed, Eric Sandeen |
|---|---|
| Next by Date: | REVIEW: Enhance xfs_repair -P option to disable libxfs xfs_buf_t locking, Barry Naujok |
| Previous by Thread: | Re: XFS: SB validate failed, Eric Sandeen |
| Next by Thread: | Re: XFS: SB validate failed, Timothy Shimmin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |