All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <breeves@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] which volume is a file on?
Date: Wed, 11 Jun 2008 09:33:25 +0100	[thread overview]
Message-ID: <484F8DD5.6010901@redhat.com> (raw)
In-Reply-To: <c873553d0806101602w30ce13d5o8daf3a02dfc34eb5@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Zarthan South wrote:
> Is there a utility or a simple way to determine which volume a file is located on.

That's more of a file system question than an LVM question and it's no
different than any other type of device: find the mount point of the
file system containing the file and then consult /proc/mounts or the
output of the mount command to determine what LV the file is on.

If you want to know where the data blocks are located physically you'll
need to do a bit more work: find the inode location, determine what
block ranges are allocated to it and then figure out how they map to
physical device regions using e.g. lvdisplay --maps. The details for
this step depend on the file system type you are using. For ext2/3 you
can determine the physical location of a file's data blocks using degbugfs.

Regards,
Bryn.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkhPjdUACgkQ6YSQoMYUY97/MwCgiyszlwRO/oYMR6ABbiITOeBU
pnMAn3JLz1XNFbVlqx2KGJsgGWfhdhYk
=MHes
-----END PGP SIGNATURE-----

  reply	other threads:[~2008-06-11  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 23:02 [linux-lvm] which volume is a file on? Zarthan South
2008-06-11  8:33 ` Bryn M. Reeves [this message]
2008-06-11 20:17   ` Zarthan South

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=484F8DD5.6010901@redhat.com \
    --to=breeves@redhat.com \
    --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 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.