From: Nir Tzachar <tzachar@cs.bgu.ac.il>
To: Jerome de Vivie <jerome.devivie@free.fr>
Cc: linux-fsdevel@vger.kernel.org, <fist@cs.columbia.edu>
Subject: Re: [FiST] a problem with dget
Date: Thu, 27 Mar 2003 10:17:03 +0200 (IST) [thread overview]
Message-ID: <Pine.LNX.4.44_heb2.09.0303271006090.2260-100000@ruby> (raw)
In-Reply-To: <3E8210E0.2FFDED78@free.fr>
> Try also to unmount the lower level fs. If there are pending dentries,
> you will see this message:
> "VFS: Busy inodes afterunmount. Self-destruct in 5 seconds.Have a
> nice day..."
>
good morning (to me its morning ... )
well, i found my problem, and it was a combination of mistakes made by me:
1. i didnt understand the semantics of the inode->i_op->lookup function.
( i used wrong return codes.. )
2. i did not increase usage count of inodes upon creation, but did
decrease it upon release (very dumb of me. )
anyway, i still get the "VFS: Busy inodes ... " msg after i umount my fs.
i dont know what im doing wrong, but the same msg also appears when im
umounting wrapfs.
any idea??
========================================================================
nir.
next prev parent reply other threads:[~2003-03-27 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 16:47 a problem with dget Nir Tzachar
2003-03-26 9:23 ` Jan Hudec
2003-03-26 9:45 ` Nir Tzachar
2003-03-26 9:57 ` Jan Hudec
2003-03-26 20:43 ` [FiST] " Jerome de Vivie
2003-03-27 8:17 ` Nir Tzachar [this message]
2003-03-28 2:01 ` Erez Zadok
2003-03-30 4:29 ` Nir Tzachar
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=Pine.LNX.4.44_heb2.09.0303271006090.2260-100000@ruby \
--to=tzachar@cs.bgu.ac.il \
--cc=fist@cs.columbia.edu \
--cc=jerome.devivie@free.fr \
--cc=linux-fsdevel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).