Messages in this thread | | | Date | Mon, 11 Mar 2002 13:47:17 +0100 | From | Stephan von Krawczynski <> | Subject | Re: BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and 2.2.21-pre3 (client) |
| |
On Mon, 11 Mar 2002 14:11:54 +0300 Oleg Drokin <green@namesys.com> wrote:
> So that's /dev/hdg1 that is reiserfs v3.5 > > > /dev/hdg1 20043416 16419444 3623972 82% /p3 > > Exported fs is on /dev/hde1. > > Hm. Strange. Are you sure you do not export /dev/hdg1?
Ok, Oleg,
I re-checked the setup with all server fs as reiserfs 3.6 and the problem stays the same.
Mar 11 13:05:07 admin kernel: reiserfs: checking transaction log (device 22:01) ... Mar 11 13:05:09 admin kernel: Using r5 hash to sort names Mar 11 13:05:09 admin kernel: ReiserFS version 3.6.25
What else can I try?
I checked the setup with another client kernel 2.4.18, and guess what: it has the same problem. I have the impression that the problem is somewhere on the nfs server side - possibly around the umount case. Trond, Ken?
Can anyone reproduce this? It should be fairly simple to check.
Regards, Stephan
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |