inside.
This of course doesn't help if your VMs are Windows or legacy versions
of Linux without btrfs support. On BSD you could try ZFS.
--
Calvin Walton <calvin.wal...@kepstin.ca>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, 2015-09-28 at 23:16 +, Hugo Mills wrote:
> On Mon, Sep 28, 2015 at 07:11:51PM -0400, Calvin Walton wrote:
> >
> > The problem with trying to use btrfs checksums to compare two
> > different
> > files is that the blocks might not match up, if only du
different
arrangements on different machines, they're not really all that useful
for doing comparisons like you want.
--
Calvin Walton <calvin.wal...@kepstin.ca>
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
output while the test is running might be informative.
On the other hand, if the CPU isn't saturated and the disk io isn't
saturated, then it's probably a scaling issue in btrfs, possibly
something like lock contention.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send
of the developers here might have some more precise information on
exactly why you're seeing such a performance difference.
As an aside, you have 192TB in RAID0? That's certainly pretty
impressive, but as soon as one disk dies, you're going to lose a *lot*
of data.
--
Calvin Walton calvin.wal
On Fri, 2015-08-14 at 12:30 -0400, Calvin Walton wrote:
On Fri, 2015-08-14 at 12:16 -0300, Eduardo Bach wrote:
Hi all,
This is my first email to this list, so please excuse any gaffe.
I am in the evaluation early stages of a new storage, an SGI MIS,
currently with two HBAs LSI
filesystem like OCFS or GFS.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
to single mode and let the
drive go fast.
Calvin.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
/dev/sda2 /mnt/btrfs
Then you can create your home directory under the top level by doing
btrfs subvolume create /mnt/btrfs/home2
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
, but not completely, empty: they still
have the small files hanging around.
In this case a balance is still necessary to clean things up.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
which version of btrfs-progs you are using...
As Bob said, this issue is caused by a desynchronization between the
state file on the drive and the kernel state. However, code was added
to btrfs-progs 3.17 to detect and correct this condition.
I'd suggest updating your btrfs-progs.
--
Calvin Walton
info (device dm-4): found 67 extents
--
To unsubscribe from this list: send the line unsubscribe linux-
btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe
.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
pattern between platters without moving the seek heads. There's
nothing you could do at the OS level which would make it faster
(besides preferring to read and write at the lower LBAs of the drive).
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line
.
* Is it more risky to leave the above errors uncorrected, or to run
btrfsck with --repair?
There probably aren't any issues on the filesystem that the runtime
btrfs code can't handle. Don't run with --repair, at least not yet.
I'm using kernel 3.14.
Thanks!
-Nikolaus
--
Calvin Walton
the filesystem doesn't actually know how much space would be freed! In
order to determine this number, the filesystem has to check all the
files in the subvolume - which is what btrfs-cleaner is doing.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe
if we can agree on this.
Instead of renaming the test suite, why not just backronym it to mean
something different? The letter x is used to mean cross in many
contexts, so xfstests could easily mean cross-filesystem tests - a
name that fits perfectly!
Only kind of joking,
Calvin.
--
Calvin Walton
an additional device to the filesystem (even e.g. a 4GB
USB flash drive is often enough) - this will add space to allocate a few
new chunks, allowing the balance to proceed. You can remove the extra
device after the balance completes.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe
zlib on most systems as a / filesystem -
it's slow to decompress compared to lzo, so it will cause slower boots
if your disk is reasonably fast.)
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
command.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
chunks and then re-check the checksum to confirm the reconstruction
was successful.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
On Mon, 2014-01-20 at 10:43 -0500, G. Michael Carter wrote:
I'm pretty sure I know the answers but just wanted confirmation.
RAID1: When it reads does it read from only one disk or does it try
to read from multiple disks?
The current implementation of RAID1 on btrfs will, with a single
that?...
In a recent thread on this mailing list:
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/31536
it looks like the decision made was that the latest btrfs-progs should
support older kernels.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux
this at the moment.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
them
for details...) may be backporting fixes themselves.
As a result, we recommend that btrfs users should generally run whatever
the latest upstream kernel release is - in particular, you should try
the latest kernel before reporting bugs in btrfs.
--
Calvin Walton calvin.wal...@kepstin.ca
the 'physical' and
'expected' values to look for gaps between fragments.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
been merged yet. It
might show up in 3.9 or 3.10.
You really should upgrade your kernel, however. 3.5.0 is rather old in
btrfs-years! Lots of fixes have gone into newer kernels.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs
and then, but there is no current support in btrfs for
it.
(One thing to note: small files are often stored in the metadata area
instead of data area, which would be raid1 in your setup. As a result,
those small files are more likely to be recoverable).
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from
applications :)
--
Calvin Walton calvin.wal...@kepstin.ca
smime.p7s
Description: S/MIME cryptographic signature
distributions have done so.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
recommendation. (Although if
you're using a EFI bios, you could just stick all the bootloader stuff
on the VFAT EFI system partition instead.)
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
that will allow
partitions (MBR/GPT) to be resized online, I think they're queued up to
be included in some upcoming linux release:
http://lwn.net/Articles/481141/
You still can't move partitions online, of course.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send
a major problem if you had backups in the first
place :)
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
but does not produce an error
either.
Looks like you've found another bug (or maybe just a missing feature);
it would be nice if this command allows you to use '0' as an alias for
the root subvolume.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line
extra code to enable doing cross-mount reflinks? Why was the
decision made not to allow them?
Is there some particular opposition to supporting cross-mount operations
on multiple mounts of the same filesystem in general? (I'd love to have
rename() work across bind mounts, for example...)
--
Calvin
or
subvolume.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
if the ratio is tunable.
But better to have a bit of unused metadata space than to get 'out of
space' errors once you've filled your disk and you're trying to delete
some files!
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs
to be recoverable, you should use a redundant raid
mode; otherwise don't expect that you'll be able to save much after a
disk failure.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
On Wed, 2012-05-23 at 16:44 +0100, Martin wrote:
On 23/05/12 05:19, Calvin Walton wrote:
On Tue, 2012-05-22 at 22:47 +0100, Martin wrote:
I've got two recent examples of SSDs. Their pristine state from the
manufacturer shows:
Device Model: OCZ-VERTEX3
00 00 00 00 00 00
,
since to rewrite a block - even if the block is partially unwritten - is
still likely to require a read-modify-write cycle with an erase step.
The granularity of the erase blocks is just too big for the savings to
be very meaningful.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe
proprietary
firmware.
Several of the Marvell devices actually have completely different
firmwares (e.g. Intel's firmware for Marvell devices was reportedly
developed by them in-house), and Intel's Sandforce firmware has some
customizations for improved reliability, at the expense of some speed.
--
Calvin
On Tue, 2012-04-10 at 11:16 -0400, Josef Bacik wrote:
On Mon, Apr 09, 2012 at 05:20:46PM -0400, Calvin Walton wrote:
On Mon, 2012-04-09 at 16:54 -0400, Josef Bacik wrote:
On Mon, Apr 09, 2012 at 01:10:04PM -0400, Calvin Walton wrote:
On Mon, 2012-04-09 at 11:53 -0400, Calvin Walton wrote
On Tue, 2012-04-10 at 18:29 +0200, David Sterba wrote:
On Tue, Apr 10, 2012 at 12:04:00PM -0400, Calvin Walton wrote:
On Tue, 2012-04-10 at 11:16 -0400, Josef Bacik wrote:
This one brings the mount time right down on my laptop, it's back to
around 0.5 seconds, same as 3.3.x.
Did you
On Mon, 2012-04-09 at 11:53 -0400, Calvin Walton wrote:
Hi,
I have a system that's using a dracut-generated initramfs to mount a
btrfs root. After upgrading to kernel 3.4.0-rc2 to test it out, I've
noticed that the process of mounting the root filesystem takes much
longer with 3.4.0-rc2
On Mon, 2012-04-09 at 16:54 -0400, Josef Bacik wrote:
On Mon, Apr 09, 2012 at 01:10:04PM -0400, Calvin Walton wrote:
On Mon, 2012-04-09 at 11:53 -0400, Calvin Walton wrote:
Hi,
I have a system that's using a dracut-generated initramfs to mount a
btrfs root. After upgrading
/dracut.git;a=blob;f=modules.d/90btrfs/80-btrfs.rules;hb=HEAD
which would be suitable with minor modifications for use in a system
udev installation as well.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
it.
Discard is handled with a separate mount option on btrfs (called
'discard'), and is disabled by default even if you have the 'ssd' option
enabled, because of the negative performance impact it has had on some
SSDs.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list
system.
Can anyone of you redirect me to that place to download the btrfsprogs
source code.
The best way to get the btrfs-progs source is probably via git; Chris
Mason's repository for it can be found at
http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs.git
--
Calvin Walton
, it means that the drive medium is deteriorating. It's very likely
that you will have additional failures in the future, resulting in more
IO errors and lost data. For your sanity, I recommend replacing a drive
as soon as you see any one error on it.
--
Calvin Walton calvin.wal...@kepstin.ca
, enabling defrag will cause files to be rewritten
occasionally, which will use additional write cycles on your flash
memory cells.
Unless you're experiencing performance problems, I would recommend you
leave the autodefrag option disabled on an SSD.
--
Calvin Walton calvin.wal...@kepstin.ca
is an empty
directory.
Hopefully this can be improved at some point :)
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
there
may have been some performance issues in certain cases with drives that
have slow trim implementations. But feel free to give it a try.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
On Wed, 2011-06-22 at 11:39 -0400, Josef Bacik wrote:
On 06/22/2011 10:15 AM, Henning Rohlfs wrote:
On Tue, 21 Jun 2011 11:24:11 -0400, Calvin Walton wrote:
On Mon, 2011-06-20 at 23:51 +0200, Henning Rohlfs wrote:
Hello,
I've migrated my system to btrfs (raid1) a few months ago. Since
enough to bisect it, so I might
give that a try. It'll be slow going, though.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
of the current subvolume state.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
the last
snapshot that references that data.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
it, do you think this would be a helpful addition?
[1]
https://btrfs.wiki.kernel.org/index.php/FAQ#Why_does_df_show_incorrect_free_space_for_my_RAID_volume.3F
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 2011-03-31 at 18:59 -0400, Josef Bacik wrote:
On Thu, Mar 31, 2011 at 05:06:42PM -0400, Calvin Walton wrote:
On Wed, 2011-03-30 at 17:19 -0400, Josef Bacik wrote:
Hello,
Just found a big bug in the free space caching stuff that will result in
early ENOSPC. I'm working
about which
kernels are affected? Is it any kernel with free space cache support (is
2.6.38.x included?) - and if so, do you plan on submitting the fix to
the stable kernel series?
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs
with it: make sure you run your own spam filters
and are careful about links in mails.
--
Calvin Walton calvin.wal...@kepstin.ca
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
be just that: an
estimate, not an exact count.)
This will get worse once btrfs supports having data with different raid
levels on the same filesystem, because you’ll have different amounts of
“available” space depending on which raid type the data in question is
stored with.
--
Calvin Walton
: total=3.62GB, used=1.93GB
ayu ~ # df -h /
FilesystemSize Used Avail Use% Mounted on
/dev/sda4 402G 254G 145G 64% /
If you use the btrfs tool's df command to account for space in your
testing, you should get much more accurate results.
--
Calvin Walton calvin.wal
to rsync
To add a bit to this: if you *do not* use the --inplace option on rsync,
rsync will rewrite the entire file, instead of updating the existing
file!
This of course negates some of the benefits of btrfs's COW support when
doing incremental backups.
--
Calvin Walton calvin.wal...@kepstin.ca
filesystem
The subvolid= mount option was missing from the wiki, so I've just added
it:
https://btrfs.wiki.kernel.org/index.php/Getting_started#Mount_Options
--
Calvin Walton calvin.wal...@gmail.com
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
:/
8--8-
From: Calvin Walton calvin.wal...@gmail.com
Date: Sat, 27 Nov 2010 23:17:55 -0500
Subject: [PATCH] Btrfs: Allow mounting sub-sub(-sub...)-volumes using
subvol=a/b/c
Currently you can only mount subvolumes which are direct children
/mountpoint/of/volume
Let us know if that helps, of course :)
--
Calvin Walton calvin.wal...@gmail.com
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
like this is pretty recent; I don't recall seeing it on
2.6.36-rc4-00076-g9c03f16. If nobody has any ideas regarding the cause,
I can try bisecting it to narrow it down; let me know!
--
Calvin Walton calvin.wal...@gmail.com
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs
to developers.)
If you think of it this way, memcpy is a function defined in the C
standard, there's absolutely nothing Linux-specific about using it.
Of course, IANAL; and you should probably grab some more opinions on the
matter.
--
Calvin Walton calvin.wal...@gmail.com
--
To unsubscribe
/udev/rules.d/64-btrfs-scan.rules or so) will cause your
btrfs to be scanned when found. Possibly something like this could be
distributed with btrfsprogs?
--
Calvin Walton calvin.wal...@gmail.com
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message
);
+ exit(1);
+ }
name = fname;
} else {
fd = open_file_or_dir(fname);
--
Calvin Walton calvin.wal...@gmail.com
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
71 matches
Mail list logo
