mkdir freezes entire file system for 30secs

Hegemon · 04-16-2009, 06:51 PM

Specifically this is happening in my Music folder which does have a fairly large number (~350) of sub directories. Other directories are fine indicating its not a hardware problem.

When I mkdir a new directory it locks up for a while. 'ls' freezes up, streaming media dies and so on. Creating a 2nd directory after the first works fine though, then if I wait a while and try again its another lock up.

fsck didn't turn up any problems.

The drive doesn't have a whole lot of other usage. I know the drive isn't spinning up or anything because sometimes I am streaming music off it.

Ubuntu Jaunty (Latest updates as of now).

Code:

Linux hextor 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 x86_64 GNU/Linux

Code:

.-(/mnt/storage1/Music)----------------------------------------(hegemon@hextor)-
`--> sudo tune2fs -l /dev/sdd1
[sudo] password for hegemon: 
tune2fs 1.41.4 (27-Jan-2009)
Filesystem volume name:   storage1
Last mounted on:          <not available>
Filesystem UUID:          318458f1-1403-4bdf-88c7-f8e361d055a8
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags:         signed_directory_hash 
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              122109952
Block count:              244190000
Reserved block count:     0
Free blocks:              787593
Free inodes:              122077550
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      965
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16384
Inode blocks per group:   512
Filesystem created:       Thu Sep 20 15:03:07 2007
Last mount time:          Fri Apr 17 07:56:58 2009
Last write time:          Fri Apr 17 07:56:58 2009
Mount count:              6
Maximum mount count:      39
Last checked:             Tue Apr  7 16:15:57 2009
Check interval:           15552000 (6 months)
Next check after:         Sun Oct  4 17:15:57 2009
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          128
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      a8ffa8f9-97fa-4e59-8402-de8662a6c321
Journal backup:           inode blocks

Undeadzz · 04-16-2009, 09:18 PM

There is 3 diffrent kernels the server,desktop, and preempt depending on what one u use there will be i/o bottleneck or throughput bottleneck. It sounds like ur using the server one, so the i/o will be greater but ur streaming music and other fancy stuff gets on a waiting list until the io/ looses up.

Hegemon · 04-21-2009, 09:59 PM

I'm using the desktop kernel, I'm switching to the server one to see if that makes a difference otherwise I'll have a look at different schedulers.

With that said, this is just a home server, its not under any huge load. It is running BitTorrent (deluge) which could be using a lot of I/O but that doesn't explain why its only the music directory that seems to be having problems, the drive/filesystem used by BitTorrent is different too.

The system also used to work on basically the same setup without problems.

Hegemon · 04-29-2009, 06:03 AM

I tried the server kernel without any difference.

Its now happening when I make a directory in any directory, not just the music one although its only on that filesystem.

Next I'll try making an ext4 partition on a different drive and putting my music on that.