I see what you're saying. Hmm, but I wonder if it would matter in my
case. The web machines surrounding the central file server are dedicated
to certain accounts. Web machines do not "rotate" in any way, so data a
-> web1, data b -> web2, etc. The only situation that would come up is
when a user is altering their information on the file server.
Hmm...
Heh, well then this just leads me to the question, how is Raid Inc.
able to offer me what I want for $10,000 when it seems impossible
at the moment. They said the only thing required is locking in the
OS the controller runs on.
Thanks
-jeremy
>
> Nope. What happens when machine A reads from the Raid array, machine B then
> writes to the portion that was just read by machine A, then another process on
> machine A wants to read that same spot again. Machine A reads the information
> directly out of cache instead of checking the disks and voila, you just got
> stale information. There is no way around this currently in Linux. This
> would require either a userspace sync daemon that worked amongst all machines
> on the bus, or a kernel level solution.
>
> > Raid Inc. wants $10,000 for their "solution". I was trying
> > to use what we already have.
>
> --
> Doug Ledford <[EMAIL PROTECTED]>
> Opinions expressed are my own, but
> they should be everybody's.
>
http://www.xxedgexx.com | [EMAIL PROTECTED]
---------------------------------------------
Y2K. We're all gonna die.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
