From: viro@parcelfarce.linux.theplanet.co.uk
To: Massimo Cetra <mcetra@navynet.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mount -o bind strange behaviour
Date: Sat, 10 Jul 2004 14:50:15 +0100 [thread overview]
Message-ID: <20040710135015.GR12308@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <002401c46682$7c355c70$e60a0a0a@guendalin>
On Sat, Jul 10, 2004 at 03:33:28PM +0200, Massimo Cetra wrote:
> I have mounted several directories with option -o bind in order to have
> some files avalaible in a chroot.
>
> Mount -o bind /dir1 /dir2
>
> Yesterday I noticed that modifying some files in /dir1 didn't cause the
> corresponding files in /dir2 to be modified.
> It happened only for one mountpoint, not for the otner similar
> mountpoints.
> Umount && mount solved the problem.
>
> The only strange thing is that some hours before i noticed this
> behaviour, machine load reached 150 (apache was overloaded)
>
> Is it a bug somewhere in the kernel ?
No way to tell without at least the contents of your /proc/mounts before and
after...
prev parent reply other threads:[~2004-07-10 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 13:33 Mount -o bind strange behaviour Massimo Cetra
2004-07-10 13:50 ` viro [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040710135015.GR12308@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mcetra@navynet.it \
/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.