| To: | Mark Magpayo <mmagpayo@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Repairing a possibly incomplete xfs_growfs command? |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Thu, 17 Jan 2008 16:19:59 -0600 |
| Cc: | David Chinner <dgc@xxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <9CE70E6ED2C2F64FB5537A2973FA4F02535954@xxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <9CE70E6ED2C2F64FB5537A2973FA4F02535951@xxxxxxxxxxxxxxxxxxxxxxxx> <478FA832.7030200@xxxxxxxxxxx> <9CE70E6ED2C2F64FB5537A2973FA4F02535954@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.9 (Macintosh/20071031) |
Mark Magpayo wrote: > Here's the entire output: > > major minor #blocks name > > 3 0 512000 hda > 3 1 511528 hda1 > 152 0 9523468862 etherd/e1.0 > 152 16 9523468862 etherd/e0.0 > 254 0 19046932480 dm-0 > > > I believe dm-0 is the lvm device. Yep, in 1k units, so: 19046932480*1024 19504058859520 and: superblock read failed, offset 19504058859520, size 2048, ag 64, rval 0 so it's trying to read a 2k (?) superblock right in the last 1k of the device? Hrm. (Dave, Barry - isn't that 2048 the sector size, not block size?) Also from your sb 0 printout: blocksize = 4096 dblocks = 11904332800 is 48760147148800, exactly 2.5x bigger than your device is. Weird. -Eric |
| Previous by Date: | RE: Repairing a possibly incomplete xfs_growfs command?, Mark Magpayo |
|---|---|
| Next by Date: | Re: Repairing a possibly incomplete xfs_growfs command?, Nathan Scott |
| Previous by Thread: | RE: Repairing a possibly incomplete xfs_growfs command?, Mark Magpayo |
| Next by Thread: | Re: Repairing a possibly incomplete xfs_growfs command?, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |