From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ivan Kanis <ivank@wrq.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
linux-kernel@vger.kernel.org, nfs-devel@linux.kernel.org
Subject: Re: [BUG] knfsd causes file system corruption when files are locked.
Date: 16 Nov 2000 15:36:21 +0100 [thread overview]
Message-ID: <shsofzg9e6y.fsf@charged.uio.no> (raw)
In-Reply-To: <14867.6967.292440.394045@jedi.wrq.com> <14867.9090.689736.462761@notabene.cse.unsw.edu.au> <14867.18905.212001.355827@jedi.wrq.com>
In-Reply-To: Ivan Kanis's message of "Wed, 15 Nov 2000 18:43:37 -0800 (PST)"
>>>>> " " == Ivan Kanis <ivank@wrq.com> writes:
Ivan> space. I am running this on ext2fs. Fsck-ing the filesystem
Ivan> does not help. The only way to recover the space is to
Ivan> reformat the partition.
Ivan>
Ivan> [3.] knfsd, lock, NLM_SHARE, NLM_UNSHARE
Ivan>
Ivan> [4.] Linux version 2.2.16 (root@jedi) (gcc version 2.7.2.3)
Please dig around in dejanews for the locking patch I posted on l-k
last week (to be applied on top of 2.2.18pre21). It fixes 3 leaks in
the locking code (amongst them the share leak).
If you can't find it, I'll be happy to post it via private mail...
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-16 15:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 23:24 [BUG] knfsd causes file system corruption when files are locked Ivan Kanis
2000-11-16 0:00 ` Neil Brown
2000-11-16 2:43 ` Ivan Kanis
2000-11-16 14:36 ` Trond Myklebust [this message]
2000-11-20 18:43 ` Ivan Kanis
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=shsofzg9e6y.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=ivank@wrq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs-devel@linux.kernel.org \
/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.