From: virtiofs-bot@sinrega.org
To: virtio-fs@redhat.com
Subject: [Virtio-fs] [virtiofsd] Issue closed: remove file from host doesn't free up the disk space.
Date: Tue, 29 Nov 2022 16:49:34 +0000 (UTC) [thread overview]
Message-ID: <42663.122112911493102330@us-mta-581.us.mimecast.lan> (raw)
Hi guys,
we are using qemu to create some sandboxes and use virtiofs to share some folders between the host and the guest. This is the command that we start the virtiofsd
`virtiofsd --syslog -o cache=auto -o no_posix_lock -o source={some path} --fd=3 -f --thread-pool-size=1`
We find out that with such settings, when we creating some file inside guest and then delete those file in the host. The disk space will not be freed until we run the `rm {file}` inside guest again and guest will report `no such file or directory` but the space is freed.
We also find out that once we change the option to `cache=none`, this wierd behavior disappears.
Is this expected. Is there a way that we can enable the cache while make the scenario that I mentioned above work?
---
https://gitlab.com/virtio-fs/virtiofsd/-/issues/64
reply other threads:[~2022-11-29 16:49 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=42663.122112911493102330@us-mta-581.us.mimecast.lan \
--to=virtiofs-bot@sinrega.org \
--cc=virtio-fs@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).