phew.. thanks resize2fs for being cool

Yesterday while shrinking a filesystem my computer got stock due a hardware failure:


[root@mirror /]# resize2fs -p /dev/mapper/vg_mirror-LogVol03 410G
resize2fs 1.41.14 (22-Dec-2010)
Resizing the filesystem on /dev/mapper/vg_mirror-LogVol03 to 107479040 (4k) blocks.
Begin pass 2 (max = 15391251)
Relocating blocks XXXXXXXXXXXXXXXXXXXXXX------------------

Booted from a DVD in the rescue environment, mounted the filesystem and everything was OK. The size was still the original. I performed an e2fsck and then tried again. Apparently, the “Relocating blocks” part doesn’t cause any corruption if interrupted 😀

Spanish

Ayer mientras achicaba un filesystem mi computadora se freezo por un problema de hardware:


[root@mirror /]# resize2fs -p /dev/mapper/vg_mirror-LogVol03 410G
resize2fs 1.41.14 (22-Dec-2010)
Resizing the filesystem on /dev/mapper/vg_mirror-LogVol03 to 107479040 (4k) blocks.
Begin pass 2 (max = 15391251)
Relocating blocks XXXXXXXXXXXXXXXXXXXXXX------------------

Bootie desde un DVD, en modo rescate, monte el filesystem y todo estaba bien. El tamaño del filesystem todavĂ­a era el original. Realice un e2fsck y despuĂ©s probĂ© de nuevo con el resize2fs. Aparentemente la parte de “Relocating blocks” no hace ningĂșn daño si se interrumpe 😀

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s