LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 08-30-2009, 06:45 PM   #1
gvsopic
LQ Newbie
 
Registered: Aug 2009
Posts: 2

Rep: Reputation: 0
Resize2fs taking too long and no HD activity apparent


Hi,
I have a system running gentoo on /dev/sda3. I booted off of a USB stick running Ubuntu and fired up gparted to resize sda3 so I could have some space to try ubuntu out for a change. It seemed alright at first running the e2fsck and showing 3.6% for non-contiguous inodes. Upto here my HD was spinning nicely and the LED for HD access was solid on for a good 15 minutes (the whole HD is 40 GB and I tried to resize /dev/sda3 from 36 to 24GB). Now it's been stuck on the resize2fs for nearly 3 hours with scarcely any HD activity. Running top, I could see that resize2fs was consuming a good bit of CPU, nearly 70%.
Any ideas?
Thanks
GV
 
Old 08-30-2009, 07:04 PM   #2
kbp
Senior Member
 
Registered: Aug 2009
Posts: 3,790

Rep: Reputation: 653Reputation: 653Reputation: 653Reputation: 653Reputation: 653Reputation: 653
Hi gvsopic,

Interrupting a partition resize operation has a high possibility of being fatal, leave it as long as you can.

.. you do have a backup dont you ?

cheers,

kbp
 
Old 08-31-2009, 02:21 AM   #3
gvsopic
LQ Newbie
 
Registered: Aug 2009
Posts: 2

Original Poster
Rep: Reputation: 0
kbp,
Thanks for the reply. Yep, leaving it be did do the trick
I was just worried I wasn't seeing much activity from the disk, I suppose resize2fs does more number crunching than disk access, though I could really find a resource to explain the lower-level intricacies of resize2fs, I assumed it was defragmenting the files that had fragments beyond the newly adjusted boundary of the partition.

Here's the output, not sure why it did so many moves and right shifts, looks like it tests the operation first and then actually carries it out...

Code:
GParted 0.3.8

Libparted 1.8.9

Move /dev/sda3 to the right and shrink it from 35.36 GiB to 24.41 GiB  07:40:09    ( SUCCESS )
     	
calibrate /dev/sda3  00:00:00    ( SUCCESS )
     	
path: /dev/sda3
start: 3970512
end: 78126047
size: 74155536 (35.36 GiB)
calculate new size and position of /dev/sda3  00:00:00    ( SUCCESS )
     	
requested start: 3971072
requested end: 55171071
requested size: 51200000 (24.41 GiB)
new start: 3971520
new end: 55170863
new size: 51199344 (24.41 GiB)
check filesystem on /dev/sda3 for errors and (if possible) fix them  00:10:06    ( SUCCESS )
     	
e2fsck -f -y -v /dev/sda3
     	
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

876603 inodes used (37.81%)
31158 non-contiguous inodes (3.6%)
# of inodes with ind/dind/tind blocks: 24524/316/0
4832925 blocks used (52.14%)
0 bad blocks
1 large file

740509 regular files
117327 directories
1049 character device files
4089 block device files
0 fifos
6898 links
13614 symbolic links (12849 fast symbolic links)
6 sockets
--------
883492 files
e2fsck 1.41.3 (12-Oct-2008)
shrink filesystem  04:21:05    ( SUCCESS )
     	
resize2fs /dev/sda3 25599671K
     	
Resizing the filesystem on /dev/sda3 to 6399917 (4k) blocks.
The filesystem on /dev/sda3 is now 6399917 blocks long.

resize2fs 1.41.3 (12-Oct-2008)
shrink partition from 35.36 GiB to 24.41 GiB  00:00:00    ( SUCCESS )
     	
old start: 3970512
old end: 78126047
old size: 74155536 (35.36 GiB)
new start: 3970512
new end: 55169855
new size: 51199344 (24.41 GiB)
check filesystem on /dev/sda3 for errors and (if possible) fix them  00:08:37    ( SUCCESS )
     	
e2fsck -f -y -v /dev/sda3
     	
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

876603 inodes used (54.60%)
32033 non-contiguous inodes (3.7%)
# of inodes with ind/dind/tind blocks: 24524/316/0
4787182 blocks used (74.80%)
0 bad blocks
1 large file

740509 regular files
117327 directories
1049 character device files
4089 block device files
0 fifos
6898 links
13614 symbolic links (12849 fast symbolic links)
6 sockets
--------
883492 files
e2fsck 1.41.3 (12-Oct-2008)
grow filesystem to fill the partition  00:00:07    ( SUCCESS )
     	
resize2fs /dev/sda3
     	
Resizing the filesystem on /dev/sda3 to 6399918 (4k) blocks.
The filesystem on /dev/sda3 is now 6399918 blocks long.

resize2fs 1.41.3 (12-Oct-2008)
calculate new size and position of /dev/sda3  00:00:00    ( SUCCESS )
     	
requested start: 3971520
requested end: 55170863
requested size: 51199344 (24.41 GiB)
new start: 3971520
new end: 55170863
new size: 51199344 (24.41 GiB)
check filesystem on /dev/sda3 for errors and (if possible) fix them  00:08:37    ( SUCCESS )
     	
e2fsck -f -y -v /dev/sda3
     	
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

876603 inodes used (54.60%)
32033 non-contiguous inodes (3.7%)
# of inodes with ind/dind/tind blocks: 24524/316/0
4787182 blocks used (74.80%)
0 bad blocks
1 large file

740509 regular files
117327 directories
1049 character device files
4089 block device files
0 fifos
6898 links
13614 symbolic links (12849 fast symbolic links)
6 sockets
--------
883492 files
e2fsck 1.41.3 (12-Oct-2008)
move filesystem to the right  02:42:48    ( SUCCESS )
     	
perform readonly test  00:59:41    ( SUCCESS )
     	
using internal algorithm
read 51199344 sectors
finding optimal blocksize
     	
read 32768 sectors using a blocksize of 128 sectors  00:00:03    ( SUCCESS )
     	
32768 of 32768 read
2.50279 seconds
read 32768 sectors using a blocksize of 256 sectors  00:00:02    ( SUCCESS )
     	
32768 of 32768 read
2.50538 seconds
optimal blocksize is 128 sectors (64.00 KiB)
read 51133808 sectors using a blocksize of 128 sectors  00:59:36    ( SUCCESS )
     	
51133808 of 51133808 read
51199344 sectors read
perform real move  01:43:07    ( SUCCESS )
     	
using internal algorithm
copy 51199344 sectors
finding optimal blocksize
     	
copy 32768 sectors using a blocksize of 64 sectors  00:00:04    ( SUCCESS )
     	
32768 of 32768 copied
4.27867 seconds
copy 32768 sectors using a blocksize of 128 sectors  00:00:04    ( SUCCESS )
     	
32768 of 32768 copied
3.93662 seconds
copy 32768 sectors using a blocksize of 256 sectors  00:00:04    ( SUCCESS )
     	
32768 of 32768 copied
4.14965 seconds
optimal blocksize is 128 sectors (64.00 KiB)
copy 51101040 sectors using a blocksize of 128 sectors  01:42:55    ( SUCCESS )
     	
51101040 of 51101040 copied
51199344 sectors copied
move partition to the right  00:00:01    ( SUCCESS )
     	
old start: 3970512
old end: 55169855
old size: 51199344 (24.41 GiB)
new start: 3971520
new end: 55170863
new size: 51199344 (24.41 GiB)
check filesystem on /dev/sda3 for errors and (if possible) fix them  00:08:48    ( SUCCESS )
     	
e2fsck -f -y -v /dev/sda3
     	
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

876603 inodes used (54.60%)
32033 non-contiguous inodes (3.7%)
# of inodes with ind/dind/tind blocks: 24524/316/0
4787182 blocks used (74.80%)
0 bad blocks
1 large file

740509 regular files
117327 directories
1049 character device files
4089 block device files
0 fifos
6898 links
13614 symbolic links (12849 fast symbolic links)
6 sockets
--------
883492 files
e2fsck 1.41.3 (12-Oct-2008)
grow filesystem to fill the partition  00:00:00    ( SUCCESS )
     	
resize2fs /dev/sda3
     	
resize2fs 1.41.3 (12-Oct-2008)
The filesystem is already 6399918 blocks long. Nothing to do!


========================================
Thanks for everything.
Cheers,
GV
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
why is the HURD taking so long? icecubeflower General 8 04-01-2009 06:25 AM
why is the HURD taking so long? icecubeflower Linux - General 1 03-31-2009 05:46 PM
Why is Resolving taking so long? DevilDust Linux - Networking 11 08-08-2004 11:55 PM
why is x taking so long to get desktop up camp freddie Debian 5 05-15-2004 06:58 AM
Seriously this is taking a long time!! Omega Linux - Newbie 13 04-25-2003 05:46 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 04:01 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration