From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: elaexuotee@wilsonb.com, 43062-done@debbugs.gnu.org
Subject: bug#43062: --expose in vm does not reflect file modifications in guest
Date: Mon, 31 Aug 2020 15:52:11 +0200 [thread overview]
Message-ID: <871rjmdit0.fsf@gnu.org> (raw)
In-Reply-To: <878sdwvvpn.fsf@cbaines.net> (Christopher Baines's message of "Sun, 30 Aug 2020 19:23:48 +0100")
Hello!
Christopher Baines <mail@cbaines.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi,
>>
>> elaexuotee--- via Bug reports for GNU Guix <bug-guix@gnu.org> skribis:
>>
>>> When using --expose to mirror a path between host and guest, the guest mirror
>>> fails to reflect file modifications from the host. However, file creation and
>>> deletion are correctly propogated.
>>>
>>> To pick up file modifications in the guest, it is sufficient to remount
>>> mirroring 9p filesystem.
>>>
>>> Is this behaviour expected?
>>
>> I believe this comes from the “cache=loose” 9p mount option added in
>> commit e0d96774dd48c29ccc4c90fea1f8f71850ab0879.
>>
>> Does the patch below help?
>>
>> Chris, what do you think? How would this affect the performance issues
>> that led to e0d96774dd48c29ccc4c90fea1f8f71850ab0879?
>
> Caching only for readonly filesystems sounds fine, I think I was only
> thinking about the store for e0d96774dd48c29ccc4c90fea1f8f71850ab0879.
Alright, I went ahead and did that in
7eeb78157d3d0267ce4a4ea38ff56a2c4246c11b.
Thanks!
Ludo’.
prev parent reply other threads:[~2020-08-31 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 2:04 bug#43062: --expose in vm does not reflect file modifications in guest elaexuotee--- via Bug reports for GNU Guix
2020-08-28 14:11 ` Ludovic Courtès
2020-08-29 6:38 ` elaexuotee--- via Bug reports for GNU Guix
2020-08-30 18:23 ` Christopher Baines
2020-08-31 13:52 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rjmdit0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43062-done@debbugs.gnu.org \
--cc=elaexuotee@wilsonb.com \
--cc=mail@cbaines.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).