Hello Alban! Alban Crequy schrieb:> No, you should use --size only on regular file for loop devices (in > this case, you must set a size in KB). But for block devices, you > should not use --size.Thanks, but then I have a problem...> About "Unable to read the size of block device": lconf is using the > file /proc/partitions to know the size of a block device. Check if > your block device is known by /proc/partitions.It''s in there: major minor #blocks name 8 0 143666192 sda 8 1 1 sda1 8 5 20482812 sda5 8 6 20482843 sda6 8 7 16386268 sda7 8 8 86301148 sda8 8 16 143666192 sdb 8 17 15623181 sdb1 8 18 128038050 sdb2 253 0 209715200 dm-0 253 1 4612096 dm-1 <== This is it.> > What kind of LVM are you using? What is the path of your block device > (/dev/...) ? Can you send your /proc/partitions file?I am using the Linux LVM tools, version 2. The path to the block device is "/dev/vgscratch/lvglustre". I quoted the /proc/partitions file above. Thanks for your support! Best wishes Christian
Alban Crequy schrieb:> The problem is that lconf run "grep lvglustre /proc/partitions", but > the file /proc/partitions refers to your block device as "dm-1" (not > as "lvglustre"), so lconf can''t find it... > > I would suggest a workaround of this bug: > > Make a block device /dev/dm-1 with the same major/minor than your > volume /dev/vgscratch/lvglustre: > > mknod /dev/dm-1 b 253 1 > > And use "/dev/dm-1" in the Lustre configuration file, instead of > "/dev/vgscratch/lvglustre". lconf will run "grep dm-1 > /proc/partitions" and hopefully it will work. >The device node already existed, so I just had to change the Lustre configuration, and it worked. Thanks for your help! Best wishes Christian
Le Tuesday 05 July 2005 à 11:37, Christian Boehme a écrit:>Hi all! > >I am using version 1.2.6 of Lustre, as included in the (patched) SuSE >SLES 9. > >When I try to set up an OST on an LVM logical volume group I get the >error: "Unable to read the size of block device" (the device can be >formatted with mkfs.ext3). So I guess I have to use the --size >parameter.No, you should use --size only on regular file for loop devices (in this case, you must set a size in KB). But for block devices, you should not use --size. About "Unable to read the size of block device": lconf is using the file /proc/partitions to know the size of a block device. Check if your block device is known by /proc/partitions. What kind of LVM are you using? What is the path of your block device (/dev/...) ? Can you send your /proc/partitions file? -- Alban
Christian Boehme wrote:>> About "Unable to read the size of block device": lconf is using the >> file /proc/partitions to know the size of a block device. Check if >> your block device is known by /proc/partitions. > > > > It''s in there: > > major minor #blocks name[...]> > 253 1 4612096 dm-1 <== This is it. > > >> >> What kind of LVM are you using? What is the path of your block device >> (/dev/...) ? Can you send your /proc/partitions file? > > > > I am using the Linux LVM tools, version 2. The path to the block device > is "/dev/vgscratch/lvglustre". I quoted the /proc/partitions file above.The problem is that lconf run "grep lvglustre /proc/partitions", but the file /proc/partitions refers to your block device as "dm-1" (not as "lvglustre"), so lconf can''t find it... I would suggest a workaround of this bug: Make a block device /dev/dm-1 with the same major/minor than your volume /dev/vgscratch/lvglustre: mknod /dev/dm-1 b 253 1 And use "/dev/dm-1" in the Lustre configuration file, instead of "/dev/vgscratch/lvglustre". lconf will run "grep dm-1 /proc/partitions" and hopefully it will work. -- Alban
Hi all! I am using version 1.2.6 of Lustre, as included in the (patched) SuSE SLES 9. When I try to set up an OST on an LVM logical volume group I get the error: "Unable to read the size of block device" (the device can be formatted with mkfs.ext3). So I guess I have to use the --size parameter. But what value do I have to use in order to format the full LVG? The value I get with "fdisk -l"? Or the value I get with df after formatting with mkfs.ext3? Something else? What will happen if I choose a size too large for the LVG? Will this endanger data on other partitions, or will it just not work? Many thanks and best regards Christian Boehme