Ok, here's some weirdness for ya'll to ponder on. I've seen it on
any recent OpenAFS version I've ran (fileserver-wise) (1.2, 1.3,
1.4), and any client I've ever used.
Let's say I delete a VERY large directory from a volume. Very
large. It's got 30,000+ files.
This takes awhile.
by what method did you determine that the volume and the fileserver are
having problems? did you look directly on the fileserver, or from
another client system? if you're looking from the same client that's
running the 'rm' or whatever commandyou're getting a biased look.
anne
Quoting
Hi, we recently had a fileserver crash because of an ecache error.
When the server came back up it had the further misfortune of a fibre
channel adapter error which prevented the drives containing the vice
partitions from coming back online. Once those issues were dealt
with, the system was again
Namei fileserver (linux?)
If so, on something like ext2, with slow directory metadata operations?
If so, guess what...
On Thu, 13 Apr 2006, Robert Banz wrote:
Ok, here's some weirdness for ya'll to ponder on. I've seen it on any recent
OpenAFS version I've ran (fileserver-wise) (1.2, 1.3,
On Apr 13, 2006, at 11:59 AM, Derrick J Brashear wrote:
Namei fileserver (linux?)
If so, on something like ext2, with slow directory metadata
operations?
If so, guess what...
So is there a better filesystem choice on linux file servers and ext2/
ext3?
On Thu, 13 Apr 2006, Matt Elliott wrote:
On Apr 13, 2006, at 11:59 AM, Derrick J Brashear wrote:
Namei fileserver (linux?)
If so, on something like ext2, with slow directory metadata operations?
If so, guess what...
So is there a better filesystem choice on linux file servers and
Could you do some rxdebug calls to the fileserver next time? So we
know why it's getting unresponsive.
It could be running out of threads. I don't expect that, but it
could be ...
The 'symptoms' seem to be, for the most part, volume-specific. Slow
response to accessing that volume,
On Thu, 13 Apr 2006, Robert Banz wrote:
... or it could be delayed by the filesystem underneath and that's the case
where we can't do anything about it.
Things look ok on that end.
And you checked that how?
Realize it would be an operation on a directory specific to the volume,
not just
Robert Banz wrote:
Could you do some rxdebug calls to the fileserver next time? So we
know why it's getting unresponsive.
It could be running out of threads. I don't expect that, but it could
be ...
The 'symptoms' seem to be, for the most part, volume-specific. Slow
response to accessing
On Thursday, April 13, 2006 09:41:49 AM -0700 Renata Maria Dart
[EMAIL PROTECTED] wrote:
Hi, we recently had a fileserver crash because of an ecache error.
When the server came back up it had the further misfortune of a fibre
channel adapter error which prevented the drives containing the
On Thu, Apr 13, 2006 at 05:49:50PM -0400, Jeffrey Hutzelman wrote:
I have to admit I'm a little curious why you switched from inode to namei
on a Solaris server...
Interestingly, I have been considering moving to solaris as my afs server
platform (from linux) and have been wondering what the
On Thursday, April 13, 2006 07:10:24 PM -0400 Dan Pritts
[EMAIL PROTECTED] wrote:
On Thu, Apr 13, 2006 at 05:49:50PM -0400, Jeffrey Hutzelman wrote:
I have to admit I'm a little curious why you switched from inode to
namei on a Solaris server...
Interestingly, I have been considering
12 matches
Mail list logo
