Ok, I have this working, though it looks like there is an error in the
display/size calculation logic. For a disk with a 1.2TB block of open
space, we have
[EMAIL PROTECTED] ~]# fdisk /dev/etherd/e1.0
The number of cylinders for this disk is set to 145925.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/etherd/e1.0: 1200.2 GB, 1200276109824 bytes
255 heads, 63 sectors/track, 145925 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/etherd/e1.0p1 1 145925 1172142531 83 Linux
which is correct. But the volumes_editpartitions.html has
/dev/etherd/e1.0p1 Unknown Partition Type (0x0) 1 1 145925
3319626179 3165.84 GB Primary -
Almost looks like an overflow (32 bit int). It is listed correctly in
volumes_physical.html now
/dev/etherd/e1.0 1117.84 GB msdos 1 (view)
It also appears that it needs the aoe disk to be blank before hand. No
problem with this, we can blow that partition away.
Joe
Rafiu Fakunle wrote:
Hi,
[....]
/dev/etherd/e1.0
/dev/etherd/e1.1
Do the block devices show up under /proc/partitions ?
in this case. They won't always start from 1, or 0.
Joe Landman wrote:
Ok, quick work-around
[EMAIL PROTECTED] ~]# conary update bc
Applying update job:
Install bc(:doc :runtime)=1.06-6-0.1
[EMAIL PROTECTED] ~]# aoe-discover
[EMAIL PROTECTED] ~]# aoe-stat
e1.0 1200.276GB eth1 up
e1.1 160.041GB eth1 up
Possibly the right thing to do in short order is to add bc into the
That's done now.
package list. Longer term we are going to need to update aoe.
Userland or kernel? I just noticed that the aoe6-v37 tarball has the userland
tools in it as well which we currently have in the aoe-tools trove. Is there a
stipulation on having the tools version match the kernel?
I'm going to push back the build of aoe6 until I can get it all working properly. I might even pull aoe completely from the 2.1 release since it's not currently possible to get the partitioning tool to recognise the devices. I'd be happy to work with you on getting this fully supported.
If this is easy to do, and you can give me a push in the right
direction, I would be happy to give you a hand with this, including
testing.
Great. We can't get all this done for Friday's release, but certainly an update within a couple of weeks should have it all working. It's going to require a small rework of the disk partitioning / display code.
R.
--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics LLC,
email: [EMAIL PROTECTED]
web : http://www.scalableinformatics.com
phone: +1 734 786 8423
fax : +1 734 786 8452 or +1 866 888 3112
cell : +1 734 612 4615
_______________________________________________
Openfiler-users mailing list
[email protected]
https://lists.openfiler.com/mailman/listinfo/openfiler-users
