| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: SAN resizing disk, no LVM |
| From: | David Sparks <daves@xxxxxxxxxxxxxxx> |
| Date: | Thu, 28 Apr 2005 12:54:15 -0700 |
| In-reply-to: | <22029.1114645639@xxxxxxxxxxxxxxx> |
| References: | <22029.1114645639@xxxxxxxxxxxxxxx> |
| Reply-to: | daves@xxxxxxxxxxxxxxx |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 1.0.2 (X11/20050330) |
> Your partition "correction" overwrote the first 512 bytes of the first > XFS superblock. Fortunately xfs_repair can recover from that condition > by using a backup superblock. How big is the superblock? Was only the superblock damaged by "fixing" the partition table with fdisk? One could just rename fdisk on machines directly attached to the storage to prevent accidental damage. (very cheesy) The reason that I'm asking these questions is that LVM does not seem to work well with resizing of the physical disks -- you need to create a new physical volume and then add that in. Thanks, ds |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | cvs server, Stewart Stafford |
|---|---|
| Next by Date: | Re: SAN resizing disk, no LVM, Michael Loftis |
| Previous by Thread: | Re: SAN resizing disk, no LVM, Chris Wedgwood |
| Next by Thread: | Re: SAN resizing disk, no LVM, Michael Loftis |
| Indexes: | [Date] [Thread] [Top] [All Lists] |