Question on size of conf files /etc/lvmconf

[Chris Magargee_2]

What drives the size of the .conf files in /etc/lvmconf? We have files ranging 800K to 4.1 MB. Some of the larger files are VG's of smaller size, i.e. less Luns/Devices. We are running into an issue with a storage migration from EMC to EMC, due to lease refresh, and we are attempting to pre-stage all the new storage thus over 50 new VG's have to be created (Oracle databases) with each .conf at 4.1 MB that adds up to 200 MB. / does not have that available. We just want to get a handle on the size of the file and what is driving it.

I know we can reload the boot disk, if needed, and make / larger in the process to accomodate these files. Of course all the old VG's .conf files will eventually go away, but they have to live together during the migration.

Thanks!
Chris

[Steven E. Protter]

Shalom,

I am not aware of any way you control the size of these files.

Therefore the method of re-loading the / disk via an ignite backup/restore is the way to go. Sounds lie you know the steps.

Its that or have less volume groups.

SEP

[Denver Osborn]

You can look at how the new volumes are created with vgcreate. Pay attention to vgcreate values for PE SIZE (-s), MAX PE PER PV (-e), MAX PV (-p), and MAX LV (-l). The larger the values, the larger the conf files can become.

If it'll get you past your migration you could move the old VG's .conf files to another filesystem. There'd be no harm in that... the files would be recreated if making any lvm changes to those VGs or running vgcfgbackup. If they're needed before the migration completes, you can also point vgcfgrestore to the moved files.

Also note I'm not talking about moving/linking /etc/lvmconf anywhere, just the *.conf files for those old VGs being migrated.

-denver

[Patrick Wallek]

I don't see any reason to reload just to do your migration. Two options come to mind:

1) Link /etc/lvmconf to some other location that has the disk space you need.

2) Create a new LV of 500 MiB or so and mount it as /etc/lvmconf. This LV would NOT have to be in VG00. It could be in a VG from a LUN on your new EMC.

[Chris Magargee_2]

Points awarded to everyone! Thank you for the responses. Most likely (which we figured we would have to do) is create a temp /etc/lvmconf just for the migration period of the time and place all the .conf in it. We understand the risk if we had to go single user and the files not being there initially. Once the migration is completed, and all the new .conf files can fit space-wise we will go back to the original /etc/lvmconf. Otherwise we will rebuild with a larger root filesystem to accomodate those files.

Regards,
Chris