Chris Mason wrote:
Anyway, Anne, could you please take a look and make sure this still
improves your performance? I think the odd results you got for 2.4.12
before were probably due to actual fragmentation against prellocated
blocks from other files. With a single writer, 2.4.13 allocates
Hi,
When I look at ReiserFS version 3.5.34 for 2.2.19, I don't see support
for inode generation numbers for NFS, and this causes problems for Linux
2.4 NFS clients. Is there a generation number patch available for
2.2.19?
Thanks,
Anne
Hi Daniel,
I do not believe this would be related. The problem I saw was ESTALE
being returned to programs using NFS V2 to access reiserfs filesystems,
after a server reboot. While rebooting the servers, the clients do
print the same syslog messages that you see because the server isn't
