[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Anaconda LVM and file system size limitations

I wrote:
> I just set up a system with a 1.4 TB RAID (on a 3Ware 7500-8), and
> have run into some limitations of Anaconda.  It seems that it is
> not possible to set up an LVM physical volume or volume group larger
> than 1 TB, nor to create ext3 (or jfs) filesystems larger than 1 TB.
> These limits seem to be hardcoded in fsset.py, in multiple lines like
>     aelf.maxSizeMB = 1024 * 1024
> It's my undertanding that there are problems with filesystems larger
> than 2 TB, but it looks like it should be easy to change the Anaconda
> limits to a higher value, such as 1536 MB or 1920 MB.  Is there any
> known problem with doing so?

Thanks to Alexandre Oliva's message pointing me to the Anaconda docs
for how to use updates.img, I've increased these to 1920 MB (patch
attached) and it seems to solve that problem.  Probably this could be
set as high as 2047 MB before causing trouble.  At 2048 MB there might
be problems with 32-bit numbers overflowing and going negative, though
I haven't tried it.  I'll open an enhancement request in Bugzilla
proposing raising it.

I also increased the default LVM physical extent size to 64MB, because
the 4MB default is ridiculously small (max. 256GB logical volume), and
have attached a second patch for that.

> I've tried creating the PV, VG, and LVs from the command line then
> installing Fedora Core 1, and Disk Druid does show them correctly.
> But after I tell it the mount points it gets an error to the effect that
> it couldn't tell the kernel about the sda3 partition (the PV).  There's
> an option to ignore the error, but of course the install doesn't work
> after that.  I'm hoping that increasing the fsset.py limits will solve
> this problem.

Unfortunately, changing the limits did NOT fix this problem.  More
specifically, the error is "Error informing the kernel about modifications
to partition /dev/sda3 - Invalid arguments".  sda3 is my LVM physical
volume.  This error happens after the message "moving (1) to step
enablefilesystems" is written to vt 1.  Note that this is the same error
I was getting *before* I patched Anaconda, so it is not something I broke.
I'm not sure how to go about debugging this, so suggestions would be very


Attachment: max_partition_size.patch
Description: Binary data

Attachment: default_lvm_pesize.patch
Description: Binary data

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]