On Thu, Jan 20, 2011 at 05:49:06PM -0500, RR wrote: > /dev/mapper/DebSparcx64--01-root 256M 78M 166M 32% / > tmpfs 2.0G 0 2.0G 0% /lib/init/rw > udev 10M 1.1M 9.0M 11% /dev > tmpfs 2.0G 0 2.0G 0% /dev/shm > /dev/mapper/DebSparcx64--01-home 30G 177M 29G 1% /home > /dev/mapper/DebSparcx64--01-tmp 368M 11M 339M 3% /tmp > /dev/mapper/DebSparcx64--01-usr 4.6G 372M 4.0G 9% /usr > /dev/mapper/DebSparcx64--01-var 2.8G 189M 2.5G 8% /var > > The question now is, if you look carefully, I only have ~37GB showing as > partitioned. Where is the remaining (72-37 GB) space? This was easy to see > in 'format' command in Solaris but doing all sort of cart-wheels in > Debian/Linux, I don't know what the heck these dm-* partitions are, which > seem to be where this missing space is, and how do I get to it to create a > valid partition out of it and mount it and use it? Let me guess: you used LVM. If you did, you can use "vgdisplay -v DebSparcx64-01" (more generically, "vgdisplay -v name-of-volume-group") as root to see how much space is allocated and free. The dm-* devices are device mapper devices; LVM uses device mapper, so one of those will be created for each logical volume. To expand a logical volume (such as one of the /dev/mapper devices listed above), use lvextend to increase the size of the logical volume, and then use resize2fs to increase the size of the filesystem on that device. If you are simply increasing the size (and not decreasing it), you needn't provide a size to resize2fs; it will automatically determine the correct size itself. If the filesystems have been created with a recent enough version of e2fsprogs, you can perform the resizing online; that is, while the filesystem is mounted and in use. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Attachment:
signature.asc
Description: Digital signature