From: Victor Mendez <vmendez@inf.uc3m.es>
To: Lista FSDevel <linux-fsdevel@vger.kernel.org>
Subject: fist + fanout dentry problem
Date: Fri, 30 May 2003 17:19:08 +0200 [thread overview]
Message-ID: <3ED7766C.7080707@inf.uc3m.es> (raw)
Hello,
Due to fist has not implemented the fan-out yet, I am working directly
in the wrapfs generated code, to add this feature.
I am having a problem:
mount -t wrapfs -o dir=/mnt/devmnt,/mnt/devmnt2 /mnt/ptomnt /mnt /ptomnt
cp /etc/hosts /mnt/ptomnt/testfile
ls -l /mnt/ptomnt
and the command hang just before a call to vfs_readdir"/mnt/ptomnt", in
strace: getdent64 after open de dir.
after reboot I can do the ls -l /mnt/ptomnt and work with the testfile
copy there, aswell as on the branches: /mnt/devmnt and /mnt/devmnt2.
Any idea?
I also have a conceptual hesitage about the exactly work of vfs with the
dentry->d_alias, that I am using for the dentry fan-out.
Any help will be pleasured.
Reagards.
--
*********************************************************
Victor Mendez.
- Universidad Carlos III de Madrid -
vmendez@inf.uc3m.es
Despacho 2.2.A.10 Tlf: 916249118
**********************************************************
reply other threads:[~2003-05-30 15:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3ED7766C.7080707@inf.uc3m.es \
--to=vmendez@inf.uc3m.es \
--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