From: Leonid Podolny <leonid99@mail.ru>
To: nfs@lists.sourceforge.net
Subject: Problems with kNFSd 2.6.5
Date: Mon, 30 May 2005 09:21:46 +0300 [thread overview]
Message-ID: <429AB0FA.6050404@mail.ru> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm not sure that this one is a correct list to report such a bug. I
experience a weird issue and I'm not sure whether it's a bug or a
feature. :)
I'm connecting a fedora core 3 (i.e. 2.6.9) client to a sles9 (i.e.
2.6.5) server. Once I perform the following (completely legal) steps,
I'm unable to unmount the disk that was once exported.
1) at the server: mount /dev/sdag1 /tmp/export
2) at the server: exportfs "*:/tmp/export" -o "rw" #note that this
export is not at the /etc/exports
3) at the client: mount server:/tmp/export /tmp/mountpoint
4) at the client: ls /tmp/mountpoint #or some other usage
5) at the client: unexport /tmp/mountpoint
6) at the server: exportfs -r # removes the export, as it is not in
the /etc/exports
7) at the server: umount /dev/sdag1 #fails, though noone uses it.
It looks like that the exportfs -r somehow fails to decrement the usage
count on the block device.
As a totally separate issue, I fail to figure out a conditions, when a
client sends a READDIR instead of a READDIR+. I've found in the sources,
that it happens once a directory size is bigger than 8 pages, but I
tried to gradually remove files to the directory at the server and
failed to return from READDIR to READDIR+.
- --
- ------------------------------------------------------------------------
Leonid Podolny | /"\
| \ / ASCII Ribbon Campaign
leonidp(at)gmail.com | x Against HTML Mail
+972-54-5696948 | / \
- ------------------------------------------------------------------------
PGP fingerprint: 51B2 F1DB 485E 2C48 2E17 94D1 7EC4 E524 B156 B9F0
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB156B9F0
- ------------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFCmrD5fsTlJLFWufARAi+EAJ9JRipo3bWHE7oc71f45fWnZONfeACffsMe
qsFffA1WB7WsApBFEjKdG4M=
=Mmgn
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2005-05-30 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 6:21 Leonid Podolny [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-29 9:18 Problems with kNFSd 2.6.5 Leonid Podolny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=429AB0FA.6050404@mail.ru \
--to=leonid99@mail.ru \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.