| 1 |
Hilco Wijbenga writes: |
| 2 |
|
| 3 |
> Yes, df -i says /portage is out of inodes. I've never run into that |
| 4 |
> before. I reran mke2fs to increase the inode count and that fixed |
| 5 |
> things. |
| 6 |
> |
| 7 |
> Would LVM somehow prevent these sort of things from happening? LVM |
| 8 |
> doesn't affect inode usage, does it? |
| 9 |
|
| 10 |
AFAIK you will gain more inodes when you increase the size. |
| 11 |
|
| 12 |
> What exactly are the advantages |
| 13 |
> of LVM? Is it just that it's easier to resize LVM partitions after the |
| 14 |
> fact? (That would, of course, already be very useful.) |
| 15 |
|
| 16 |
Mainly. But it also allows you to create snapshots, I use this often to make |
| 17 |
backups without needing to boot from a live-cd - I can even start emerges |
| 18 |
meanwhile, but the backup will have the state the file system was in when |
| 19 |
the snapshot was taken. |
| 20 |
And you can create logical volumes that reside on partitions on different |
| 21 |
physical drives. Or you could move logical volumes from one drive or |
| 22 |
location to another one, while being in use all the time, without the need |
| 23 |
to unmount the file system. |
| 24 |
I also like the naming scheme (/dev/<volume group>/<logical volume>/ instead |
| 25 |
of /dev/sd<X><N>), although you can also use file system labels so this is |
| 26 |
not a big problem. |
| 27 |
|
| 28 |
Wonko |
Archives