I appeal to the larger community...
I am running an ASUS k8ne with a mirrored boot drive, and a 4 disk raid5 array
(total of 6). Approximately two weeks ago the raid5 array (reiser - lvm2 -
raid5) kicked out a drive, which I reinserted (three hour rebuild). Shortly
thereafter (this is my
Greetings,
I found that for reisfer filesystems sometimes the option nolargeio=1 is added
to the fstab entry. At first blush this seems to be a workaround for a kernel
bug. Does anyone have any more information ? I am running reiser - lvm2 -
raid5 currently.
regards,
-Peter
-
To unsubscribe
Greetings All,
I have been lurking for a while I recently put together a raid 5 system
(Asus K8NE SIL 3114/2.6.8.1 kernel) with 4 300GB SATA Seagate drives (a lot
smaller than the bulk of what seems to be on this list!). Currently this is
used for video and mp3 storage, being Reiser on
Good point about maxing out the pci bus... - I already use the nForce for
mirrored boot drives, so that's not an option. The IDE controllers are empty at
the moment (save for a DVD drive); I will give this a thought.
Thanks for the feedback,
-P
-Original Message-
From: [EMAIL
