Messages in this thread | | | Date | Thu, 13 Dec 2001 17:21:31 +0100 (CET) | From | Roy Sigurd Karlsbakk <> | Subject | Re: [BUG?] RAID sub system / tux |
| |
hi
Just wanted to say I've reproduced the error in tux-D1.
thanks for any help
roy
On Thu, 13 Dec 2001, Roy Sigurd Karlsbakk wrote:
> hi all > > After testing this for a while, I'm quite sure there's some kind of bug > that locks up I/O under heavy traffic. > > Hardware configuration: > > 1xAthlon 1133 > 1GB RAM > 1 20G boot disk > 2 120G ide drives on a promise ata133 (20269) controller > > Kernel: Vanilla 2.4.16 + tux-D0 > > /etc/raidtab: > > raiddev /dev/md0 > raid-level 0 > nr-raid-disks 2 > persistent-superblock 0 > chunk-size 4096 > > device /dev/hde > raid-disk 0 > device /dev/hdg > raid-disk 1 > > IDE readahead setting: > > echo file_readahead:1024 > /proc/ide/hd[eg]/settings > (I've tried down to 256 with no change.) > > file system: independant. I've tried with xfs and ext2 and get the same > result. > > Testing: > I make some 100 files, each ~1GB, and start ~100 wget processes to > retrieve data from http://localhost/file-nnnn. Each process is retrieving > a separate file, as to simulate the app. Usually, this works fine in the > beginning, but after a while it all locks up, and the [TUX worker] > (mother) process stops giving me any data, and starts using 100% system > time. If I restart tux, I can do some data retrieval for some time, but > then it locks up again. It's easily reproducable to just start, say, 50 > wget processes, killall wget, and then restart the 50 wget processes. > > Thanks for all help > > regards > > roy > > -- > Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA > > Computers are like air conditioners. > They stop working when you open Windows. > > > > > _______________________________________________ > tux-list mailing list > tux-list@redhat.com > https://listman.redhat.com/mailman/listinfo/tux-list >
-- Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA
Computers are like air conditioners. They stop working when you open Windows.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |