Hi
I can not speak about XFS on DELL with AMI MegaRAID but I'm using
RedHat 6.2 on some machines and they are terrible slow. I also
downloaded
the custom kernel from the DELL support page but nothing changed.
I remember that when I installed the first machine I wanted to call
DELL support so they replace the machine. But later I found out that
every machine was the same.
The only thing I can say is: Don't use any hardware RAID if you want
to get most perfomance out of your disks. Some years ago hardware did
improve performance but with the CPU power we have today, software RAID
is the fastet.
That's my experience, anyone to comment on this?
Simon
Dave Sill schrieb:
>
> I installed XFS 1.0 + Red Hat 7.1 via the SGI installer on a 2-proc
> Dell server with 2 x 250GB AMI MegaRAID's. The installation went
> smoothly, but I've been getting occasional messages like:
>
> May 17 03:39:08 daacsnfs kernel: __alloc_pages: 2-order allocation failed.
> May 17 03:39:08 daacsnfs kernel: __alloc_pages: 2-order allocation failed.
> May 17 03:42:52 daacsnfs kernel: __alloc_pages: 0-order allocation failed.
>
> What do these messages mean?
>
> I'm migrating one of the RAID's to xfs and it's going rather slowly
> (6 hrs to untar 18 GB so far). Watching the disk space used on the xfs
> raid, I see lots of periods with no obvious activity. E.g., at
> 5-second intervals:
>
> 248533712 13932188 234601524 6% /smm1
> 248533712 13934712 234599000 6% /smm1
> 248533712 13936248 234597464 6% /smm1
> 248533712 13936248 234597464 6% /smm1
> 248533712 13936248 234597464 6% /smm1
> 248533712 13936780 234596932 6% /smm1
> 248533712 13951096 234582616 6% /smm1
> 248533712 13951096 234582616 6% /smm1
> 248533712 13962360 234571352 6% /smm1
> 248533712 13974288 234559424 6% /smm1
> 248533712 13974328 234559384 6% /smm1
> 248533712 13974328 234559384 6% /smm1
> 248533712 13974328 234559384 6% /smm1
> 248533712 13974328 234559384 6% /smm1
> 248533712 13974328 234559384 6% /smm1
> 248533712 13993080 234540632 6% /smm1
>
> The __alloc_pages errors are much less frequent than the I/O pauses,
> so they could be two separate problems.
>
> hinv says:
>
> Main memory size: 896 Mbytes
> 2 GenuineIntel Pentium III (Katmai) processors
> 1 vga+ graphics device
> 1 keyboard
> PCI bus devices:
> ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 2).
> IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 1).
> USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 1).
> Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 2).
> VGA compatible controller: ATI Technologies Inc 3D Rage Pro (rev 92).
> PCI bridge: Intel Corporation 80960RP [i960 RP Microprocessor/Bridge]
> (rev 3).
> PCI bridge: Intel Corporation 80960RP [i960 RP Microprocessor/Bridge]
> (#2) (rev 3).
> PCI bridge: Intel Corporation 80960RP [i960 RP Microprocessor/Bridge]
> (#3) (rev 3).
> I2O: Intel Corporation 80960RP [i960RP Microprocessor] (rev 3).
> I2O: Intel Corporation 80960RP [i960RP Microprocessor] (#2) (rev 3).
> I2O: Intel Corporation 80960RP [i960RP Microprocessor] (#3) (rev 3).
> Host bridge: Intel Corporation 450NX - 82451NX Memory & I/O Controller
> (rev 3).
> SCSI storage controller: Adaptec AHA-2940U2/W / 7890 (rev 0).
> SCSI storage controller: Adaptec AHA-2940U2/W / 7890 (#2) (rev 0).
> SCSI storage controller: Adaptec AIC-7860 (rev 3).
> Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 8).
> Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (#2) (rev
> 8).
> Host bridge: Intel Corporation 450NX - 82454NX/84460GX PCI Expander
> Bridge (rev 4).
> Host bridge: Intel Corporation 450NX - 82454NX/84460GX PCI Expander
> Bridge (#2) (rev 4).
> Host bridge: Intel Corporation 450NX - 82454NX/84460GX PCI Expander
> Bridge (#3) (rev 4).
>
> --
> Dave Sill <MaxFreedom@xxxxxxxxxxxxxxxxx> <http://web.infoave.net/~dsill>
> Oak Ridge National Lab, Workstation Support
> <http://www.lifewithqmail.org>: almost everything you always wanted to know.
--
Simon Matter Tel: +41 61 695 57 35
Fr.Sauter AG / CIT Fax: +41 61 695 53 30
Im Surinam 55
CH-4016 Basel [mailto:simon.matter@xxxxxxxxxxxxxxxx]
|