From: "Linda A. Walsh" <lvm@tlinx.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] buffers shared between different devs? (was: howto speed-up thinpool-devices?)
Date: Sat, 28 Sep 2013 13:42:06 -0700 [thread overview]
Message-ID: <52473F1E.80704@tlinx.org> (raw)
In-Reply-To: <5225B49B.6050904@redhat.com>
On 9/3/2013 3:06 AM, Marian Csontos wrote:
> Buffers may be more relevant metric as the I/O among snapshots is
> "shared" on block device level.
----
I am not going to say this isn't true, BUT, some parts of the kernel seem to
report different block numbers for files on the same device when you mount
the same device (or possible subtrees of a same device) at alternate mount
points via "bind".
I have my "/usr/share" physically located on my "/home" partition under
"/home/share". In moving files from /usr/share/<subdir> to
/home/share/<subdir2>, the coreutils "mv" cmd, actually does a file copy
-- vs. when a file is detected as being on the same device, it usually
does a simple rename.
If 'mv' is seeing different device id's for a file, it's *less probable*,
but possible that such misinformation could exist at lower levels in the
kernel (?). Do you know whether or not the kernel "knows" they are on the
same device, or is it possible the buffer area of the kernel has the same
bug as the upper level that is reporting different devices to "mv"?
next prev parent reply other threads:[~2013-09-28 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-24 8:42 [linux-lvm] howto speed-up thinpool-devices? Oliver Rath
2013-09-03 10:06 ` Marian Csontos
2013-09-28 20:42 ` Linda A. Walsh [this message]
2013-09-03 10:54 ` Zdenek Kabelac
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=52473F1E.80704@tlinx.org \
--to=lvm@tlinx.org \
--cc=linux-lvm@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 NNTP newsgroup(s).