On 04/08/15 at 04:03pm, Baoquan He wrote:
On 04/08/15 at 02:52pm, Minfei Huang wrote:
> On 04/08/15 at 02:03pm, Baoquan He wrote:
> > On 04/08/15 at 12:30am, Minfei Huang wrote:
> > > The filesystem support the device to be mounted different mount points.
> > ^ Please add a "on"
> > here.
> > > The root path in the device may be different, if the mount point is
> > > mounted by bind mode. In order to dump core correctly, we should find
> > ^ change it to "in". ^ change it to vmcore.
> > > the root path in the device.
> > >
> > > Following is the case that device is mounted by bind mode.
> > >
> > > TARGET SOURCE FSTYPE OPTIONS
> > > /mnt/ext4 /dev/vda btrfs rw,relatime,seclabel,space_cache
> > > TARGET SOURCE FSTYPE OPTIONS
> > > /mnt/bind-dir /dev/vda[/var] btrfs rw,relatime,seclabel,space_cache
> > >
> > > We can find that /mnt/bind-dir is mounted in the path /dev/vda[/var], in
> > > the other word, the /mnt/bind-dir points to the /var directory in the
> > > /dev/vda.
> > > The /mnt/ext4 is the root path in the device.
> >
> > What do you mean here? In the end who is the mount point you want to
> > get? Please describe it clearly. Make people who don't talk to you face
> > to face can understand it.
> >
>
> Hi, bao.
>
> Thank you for your review.
>
> We can find that /mnt/bind-dir is a bind mounted directory which points
> to the /dev/vda[/var], meanwhile, the device /dev/vda is mounted on
> directory /mnt/ext4. So the bind mounted directory /mnt/bind-dir points
> to the /mnt/ext4/var.
Then what's the mount point you get? You tell a series of analysis,
what's the result?
Could you please assume a reviewer who didn't follow this issue want to
help review this patchset and get into it quickly? The reason for this
is we can recall these later by checking the commit log. I often forget
the details several months later.
Hi, bao.
I just show the view what bind mounted is. Where the real location is, if
the path is bind mounted.
Thanks
Minfei