We are not having a good day here in XFS land!
> hi,
>
> I have a machine at work which is a PIII 450 with 128MB ram and a 15GB IDE
> disk that will oops on the moment That I am trying to write large amounts
> of data on a samba share.
> The samba share is located on /home which is a XFS partition most of the
> times it happens about the time that the system runs out of ram buffer (eg
> 100MB) and then oopses mentioning swapper.
Samba itself does not do anything special - it just does writes to push
data out. Are you using kio or kiocluster in the mount options?
>
> 2.4.0-XFS (before 2.4.1 merge) does boot and takes the punishment with ease.
> Unfortunately I can not send the oops because:
> - The file is on the disk there.
> - The machine is currently displaying another oops
> - I can not reboot it on untill tommorow when I get to work.
>
> I can also trigger a oops using the Eicon Diva server which it contains.
> The drivver is lost after sending a fax. Open minicom on the isdn device.
> Modem init goes OK and as soon as I type atdt 000 and enter it oopses.
> Although the oops says swapper is involved I don't see the link.
> These are things that started happening after the 2.4.1 merge.
> This machined has been rock stable for the past testing period.
This problem has got to be a generic linux problem - not xfs (I hope).
>
> Sarcastic side Note: This $1800 desktop machine with samba beats a $10.000
> dell poweredge 2400 with twice the amount of ram and disk space with raid
> 10 on 4 18GB 10KRPM disks. ... by a factor of 5 that is using the 2.4.0-XFS
> kernel.
Can you elaborate on this - is this an XFS is slower than yyy or is this a
dell is slower than xxx?
And now the baby monitor is calling, I have to go be 'da da' ;-)
Steve
> Now my boss is not happy anymore (concerning NotToday)
>
> Bye
> --
> Seth
> Has anybody seen my lightbulb?
> I _really_ need some light here.
|