Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]


I've just started playing with the LVM stuff added in December, and I'm running into some issues - perhaps someone can point out either what I'm doing wrong or where the process itself is flawed.

I started off by building -current (as of yesterday) with MKLVM, so libdevmapper and lvm userland bits are installed. My kernel is fairly close to GENERIC (some extra debugging, mostly).

For this testing, I'm planning on using various pieces of wd1, a 750GB SATA disk. First step will be a single partition:

5 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
c: 1465149105 63 unused 0 0 # (Cyl. 0*- 1453520) d: 1465149168 0 unused 0 0 # (Cyl. 0 - 1453520) e: 1465149100 68 unknown # (Cyl. 0*- 1453520)

...I'll be using /dev/rwd1e (yes, the offset is weird. disklabel ickiness that I didn't feel like dealing with)

After boot, I load the devmapper:

# modload dm

Then, try to pvcreate:

# lvm pvcreate /dev/rwd1e
  /dev/log: open failed: Operation not supported
  /dev/wd0a: open failed: Device busy
  Device /dev/rwd1e not found (or ignored by filtering).

Meanwhile, the kernel messages spout a bunch of:

WARNING: module error: modcmd function returned error 17 for `vnd'

...and pvdisplay now shows:

# lvm pvdisplay
  /dev/log: open failed: Operation not supported
  /dev/wd0a: open failed: Device busy

Any help is appreciated.


Home | Main Index | Thread Index | Old Index