Hi,
Ragnar Kjørstad wrote:
On Thu, Aug 16, 2001 at 06:44:56PM +0200, Philippe Gramoulle wrote:
Has someone already created volumes above 1 terabytes ?
Yes, of course :)
Great ! What hardware/ drivers did you use ?
For now linux is using 32bit sector indexing. This will limit you to
On Thu, Aug 16, 2001 at 10:02:09PM +0200, Philippe Gramoulle wrote:
Ragnar Kjørstad wrote:
On Thu, Aug 16, 2001 at 06:44:56PM +0200, Philippe Gramoulle wrote:
Has someone already created volumes above 1 terabytes ?
Yes, of course :)
Great ! What hardware/ drivers did you use ?
The starvation occurs when some process sends large requests to the same scsi
controller as our journal replay which sends one block requests, and the one
block requests starve. Raid-resync is one known instance where this happens.
Edward's patch cures that instance.
Hans
Edward Shushkin
Doesn't look like any Reiserfs changes made it into 2.4.9. Imo I'm safer
running the -ac branch on my Reiserfs machines.
---
Dan Chen [EMAIL PROTECTED]
GPG key: www.cs.unc.edu/~chenda/pubkey.gpg.asc
On Thu, 16 Aug 2001, Yves Glodt wrote:
2.4.9 seems to be out
Got any
So I bet you that our patches that you assembled didn't go in simply because he
was packing suitcases, and not for any reason deeper than that. We'll try for
2.4.10.
Hans
Edward Shushkin wrote:
It looks like you got the worst case when the system tries to find
valid transaction
(when your fs is just created or you have fs that was non-cleanly
unmounted)
and reads all journal blocks during raid5-resync process that causes a
large number
of IO requests. If
Hello,
I have been getting the following warning:
vs-5380: reiserfs_delete_solid_item: [-1 220 0x1 IND] not found
I am currently running kernel version 2.4.7, with the latest
2.4.7-unlink-truncate-rename-rmdir patch. It looks like the
cause of this warning was introduced by the unlink
