Re: dm-mirror/kmirrord oops

[Cyril Chaboisseau <cyril.chaboisseau@free.fr>]

 Le 27 June vers 13:57, Jakob Oestergaard écrivait:
> Is your root filesystem mounted on an LV in 'vg' ?

no it's not

everything but / and /boot were in LVM

Sys. de fich.        1K-blocs       Occupé Disponible Capacité Monté sur
/dev/sda1               918322    263155    606171  31% /
tmpfs                   511064         0    511064   0% /dev/shm
/dev/sda3               233366     31130    189786  15% /boot
/dev/mapper/vg-tmp     1032088     32960    946700   4% /tmp
/dev/mapper/vg-usr     6192704   3577264   2300868  61% /usr
/dev/mapper/vg-var     2064208    679576   1279776  35% /var
/dev/mapper/vg-vcache
                       2064208    102568   1856784   6% /var/cache
/dev/mapper/vg-ulocal
                       6192704   2311668   3629380  39% /usr/local
/dev/mapper/vg-home   16513960   4829176  10845924  31% /home
tmpfs                    10240      3332      6908  33% /dev

this is the new layout but it was pretty much the way things were
organised


> But on another note; you should not have your root (or at least /etc)
> filesystem on LVM - because the LVM backup/recovery files are written
> there, and if LVM screws up completely, you'll then have no way of
> recovering (since the recovery files you need to get LVM going are
> stored via. LVM).

I thing that not having / in LVM saved my datas !
(I was indeed able to boot with a Knoppix and comment out the
problematic partitions)

> I always create a partition for / and keep /boot, /sbin, /lib and /etc
> there.
> 
> Then, I create another partition and make it a PV, put /var, /usr and
> everything else on LVM.

indeed

> That way I can pvmove anything without running into the bug you
> (probably) saw, and I will be able to recover the LVM in case it screws
> up (which I haven't seen yet).

in my case, I really thing that there was a problem with pvmove/kmirrord
when it tried to move data when they were being accessed

now, this is just a _wild_ guess after spending the whole afternoon
trying to recover my disks and I have no hard figures to back this 
speculation

I just realized that when I finally let pvmove finish it's work
everything went fine while previously every single attempt to copy data
to a new disk failed one way or another the same way : Oops in the
kernel

-- 
	Cyril Chaboisseau
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/