Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Sat, Jan 19, 2013 at 10:02:28AM +0100, Abdelkarim Mateos Sanchez wrote: > Hi. > > Desesperate. > > Try : > > Stop and deactivate DRBD (modules, service) > > Nothing work. > > LVM Logical volumes are marked with DRBD Sysme, and can't work with then for try a restore kernel panic or almost, get data. > > fsck /dev/pve/vm-100-disk-1 > fsck from util-linux-ng 2.17.2 > fsck: fsck.drbd: not found > > mount /dev/pve/vm-100-disk-1 /mnt/100/ > mount: unknown filesystem type 'drbd' > > > On google nay question about this big problem… > > Primary and Secondary disk are destroyed and marked "drbd" system… Nope. blkid is smart enough to *help* most people using drbd to not mount their file systems bypassing DRBD, because that would lead to data corruption, as DRBD cannot see IO bypassing it, and thus not replicate it. What you really should do is, promote that DRBD to primary, and mount the DRBD (not the lower level device). If you actually *intend* to bypass DRBD, knowing that you will need to do a full sync once you want to have working replication back, you may mount the lower level device directly, by explicitly specifying the file system to be used. "mount -t ext4" (or whatever). -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed