https://bugzilla.novell.com/show_bug.cgi?id=749946
https://bugzilla.novell.com/show_bug.cgi?id=749946#c4
Thomas Fehr changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
InfoProvider| |bluedzins@wp.pl
--- Comment #4 from Thomas Fehr 2012-03-12 12:13:40 UTC ---
In general there is no problem extending the size of a logical volume
with an ext4 filesystem on it while it is mounted. I did that numerous
times and it always worked flawlessly.
If I am correctly analyzing the y2log files you did the following:
You extend the logical volume /dev/dodatkowa/arch from about 2.5 TB to 5.06 TB
since YaST2 detected an ext4 fs on the logical volume which is capable of
online resizing, YaST2 automatically resizes the filesystem after resizing the
logical volume by calling resize2fs.
In your case I can see that the resize of the logical volume
/dev/dodatkowa/arch
to 5.06 TB succeeds. Afterward YaST2 called resize2fs, this apparently creates
lots of IO and needs a long time to succeed. I do not see in the y2log file
that resizefs exited, so I assume you booted the machine before resize2fs
finished. Of course aborting a running resize2fs command most certainly
leaves the resized filesystem in an inconsistent state, so this explains that
fsck was run later on the logical volume.
Unfortunately I do not have 5 Terabyte unused disk space available, but
I will try to do such a resize with a 1TB disk and see how much time it needs
and how the machine behaves while it is running.
Could you look into /var/log/messages if there are kernel error messages
at the time you did the resize.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.