Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hugo Mills <hugo-lkml@carfax.org.uk>
To: Roman Kapusta <roman.kapusta@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Space used by snapshot
Date: Thu, 17 Feb 2011 11:16:02 +0000	[thread overview]
Message-ID: <20110217111602.GF5484@carfax.org.uk> (raw)
In-Reply-To: <AANLkTi=LE2poDR5sNyPJF6rQ_TpLv5pjgHRQXG0Wpt-i@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 947 bytes --]

On Thu, Feb 17, 2011 at 12:13:53PM +0100, Roman Kapusta wrote:
> Hello all,
> 
> Is there any way how to obtain information how much space is
> physically allocated by given subvolume?
> I cannot find any. I'm interested in two values:
> 
> - physical space allocated by SUBVOLUME INCLUDING all space shared by
> other subvolumes
> 
> - physical space allocated by SUBVOLUME EXCLUDING all space shared by
> other subvolumes
> 
> Currently I can use only du, which is not reporting what I want to know.

   Not at the moment. It shouldn't be too difficult to implement
(certainly to implement the latter), but it's just not been done yet.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
  --- What do you give the man who has everything? -- Penicillin is ---  
                             a good start...                             

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2011-02-17 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 11:13 Space used by snapshot Roman Kapusta
2011-02-17 11:16 ` Hugo Mills [this message]
2011-02-17 11:54 ` Hubert Kario
2011-02-17 12:38   ` Roman Kapusta
2011-02-17 13:11     ` Hubert Kario

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=20110217111602.GF5484@carfax.org.uk \
    --to=hugo-lkml@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=roman.kapusta@gmail.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