On 02/24/2009 06:15 PM, Matthew Moore wrote:
On Tuesday 24 February 2009 02:44:14 pm Ron Johnson wrote:
[snip]
No, I definitely have /sbin/fsck.ext4.
But running it doesn't fix the group descriptor error? This person is having the
same problem and looks to have resorted to dumping the fs and
On Tuesday 24 February 2009 02:44:14 pm Ron Johnson wrote:
> This looks reasonable.
> # lvdisplay
> Logging initialised at Tue Feb 24 15:42:45 2009
> Set umask to 0077
> lvdisplayFinding all logical volumes
> lvdisplay --- Logical volume ---
> lvdisplay LV Name/dev/m
On 02/24/2009 03:34 PM, Matthew Moore wrote:
On Tuesday 24 February 2009 11:49:26 am Ron Johnson wrote:
Though, are there any commands which would indicate whether my LV or
VGs are screwed up? (Fixing them might allow me to get my data back.)
Do you think that your volume descriptors got hose
On Tuesday 24 February 2009 11:49:26 am Ron Johnson wrote:
> Though, are there any commands which would indicate whether my LV or
> VGs are screwed up? (Fixing them might allow me to get my data back.)
Do you think that your volume descriptors got hosed? The main LVM diagnostic
commands are:
pv
On 02/24/2009 06:21 AM, Mark Allums wrote:
Mark Allums wrote:
Ron Johnson wrote:
On 02/23/2009 01:52 AM, Mark Allums wrote:
[snip]
0. I have lvm2 running on top of Linux md RAID, and don't actually
have any ext4 file sytem partitions to check, so that particular
fsck command was destined t
Mark Allums wrote:
Ron Johnson wrote:
On 02/23/2009 01:52 AM, Mark Allums wrote:
[snip]
0. I have lvm2 running on top of Linux md RAID, and don't actually
have any ext4 file sytem partitions to check, so that particular fsck
command was destined to fail. But it shows it's there, when it's
Ron Johnson wrote:
On 02/23/2009 01:52 AM, Mark Allums wrote:
[snip]
0. I have lvm2 running on top of Linux md RAID, and don't actually
have any ext4 file sytem partitions to check, so that particular fsck
command was destined to fail. But it shows it's there, when it's needed
Except this
On 02/23/2009 01:52 AM, Mark Allums wrote:
[snip]
0. I have lvm2 running on top of Linux md RAID, and don't actually have
any ext4 file sytem partitions to check, so that particular fsck command
was destined to fail. But it shows it's there, when it's needed.
Except this was a virgin fs, w
Ron Johnson wrote:
On 02/22/2009 08:38 PM, Mark Allums wrote:
Ron Johnson wrote:
Hi,
# mount -v -t ext4 /dev/main_huge_vg/main_huge_lv /data/big
$ dmesg | tail -n2
EXT4-fs: ext4_check_descriptors: Block bitmap for group 0 not in
group (block 3120627712)!
EXT4-fs: group descriptors corrupted
On 02/22/2009 08:38 PM, Mark Allums wrote:
Ron Johnson wrote:
Hi,
# mount -v -t ext4 /dev/main_huge_vg/main_huge_lv /data/big
$ dmesg | tail -n2
EXT4-fs: ext4_check_descriptors: Block bitmap for group 0 not in group
(block 3120627712)!
EXT4-fs: group descriptors corrupted!
Can I just do th
Ron Johnson wrote:
Hi,
# mount -v -t ext4 /dev/main_huge_vg/main_huge_lv /data/big
$ dmesg | tail -n2
EXT4-fs: ext4_check_descriptors: Block bitmap for group 0 not in group
(block 3120627712)!
EXT4-fs: group descriptors corrupted!
Can I just do this?
# e2fsck /dev/main_huge_vg/main_huge_lv
11 matches
Mail list logo
