sequential IO isn't cached. So I think you can get a big
boost in responsiveness with a relatively small bcache size.
Chris Murphy--
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
blocks aren't reused until data is
committed to the backing device.
Chris Murphy--
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 Dec 30, 2013, at 10:10 AM, Marc MERLIN m...@merlins.org wrote:
If one day, it could at least work on a subvolume level (only sync a
subvolume), then it would be more useful to me. Maybe later…
Maybe I'm missing something, but btrfs send/receive only work on a subvolume
level.
Chris
On Dec 30, 2013, at 10:57 AM, Marc MERLIN m...@merlins.org wrote:
On Mon, Dec 30, 2013 at 10:48:10AM -0700, Chris Murphy wrote:
On Dec 30, 2013, at 10:10 AM, Marc MERLIN m...@merlins.org wrote:
If one day, it could at least work on a subvolume level (only sync a
subvolume), then it would
4793
Jan 01 21:45:09 home kernel: btrfs: open_ctree failed
If you previously tried -o recovery, before btrfsck did you try btrfs-zero-log
and if so what were the results in console and in dmesg?
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
On Jan 1, 2014, at 3:35 PM, Oliver Mangold o.mang...@gmail.com wrote:
On 01.01.2014 22:58, Chris Murphy wrote:
On Jan 1, 2014, at 2:27 PM, Oliver Mangold o.mang...@gmail.com wrote:
I fear, I broke my FS by running btrfsck. I tried 'btrfsck --repair' and it
fixed several problems
Btrfs volume without replacing the prior rootfs until later if you wish. You
aren't required to delete it, you only required to make a new one. I'm
uncertain how Debian implements this in their installer.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs
on the to do, some of which maybe should be done before
auto degraded mount, for example the hot spare work.
https://btrfs.wiki.kernel.org/index.php/Project_ideas#Multiple_Devices
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
,degraded
I would not make this option persistent by putting it permanently in the
grub.cfg; although I don't know the consequence of always mounting with
degraded even if not necessary it could have some negative effects (?)
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe
efficient snapshot behavior.
Chris Murphy--
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
messages in dmesg so you get when you use recovery?
Chris Murphy--
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
step in
repairing a problem Btrfs volume is to use -o recovery, for more information
see Btrfs FAQ url for additional problem solving recommendations.
?
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More
rather than list.
Chris Murphy--
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 Jan 3, 2014, at 7:59 PM, Jim Salter j...@jrs-s.net wrote:
On 01/03/2014 07:27 PM, Chris Murphy wrote:
This is the wrong way to solve this. /etc/grub.d/10_linux is subject to
being replaced on updates. It is not recommended it be edited, same as for
grub.cfg. The correct way is as I
it seems.
Chris Murphy
--
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
and
posting those results if you haven't already.
Chris Murphy
--
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 Jan 4, 2014, at 2:16 PM, Jim Salter j...@jrs-s.net wrote:
On 01/04/2014 02:18 PM, Chris Murphy wrote:
I'm not sure what else you're referring to?(working on boot environment of
btrfs)
Just the string of caveats regarding mounting at boot time - needing to
monkeypatch 00_header
On Dec 31, 2013, at 4:46 AM, Sulla su...@gmx.at wrote:
Dear all!
On my Ubuntu Server 13.10 I use a RAID5 blockdevice consisting of 3 WD20EARS
Sulla is this md raid5? If so can you report the result from mdadm -D
mddevice, I'm curious what the chunk size is. Thanks.
Chris Murphy
with rootfs. Using Btrfs within the VM I
still get the features I expect and the performance is quite good.
Chris Murphy
--
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
and any other nearby btrfs messages.
https://www.kernel.org/doc/Documentation/sysrq.txt
Chris Murphy--
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 Jan 5, 2014, at 4:48 PM, Chris Murphy li...@colorremedies.com wrote:
On Jan 5, 2014, at 2:17 PM, Sulla su...@gmx.at wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Chris!
Certainly: I have 3 HDDs, all of which WD20EARS.
These drives don't have a configurable SCT ERC
being reset by the kernel and if so, post the full output of that.
Chris Murphy--
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 Jan 5, 2014, at 5:15 PM, Chris Murphy li...@colorremedies.com wrote:
On Jan 5, 2014, at 3:36 PM, Brendan Hide bren...@swiftspirit.co.za wrote:
WD Greens (Reds too, for that matter) have poor non-sequential performance.
An educated guess I'd say there's a 15% chance this is a major
or not. In this case 3.11 is EOL already, no more updates.
Chris Murphy--
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
want to create a start up
script for it.
Chris Murphy
--
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 Jan 6, 2014, at 3:20 AM, Chris Samuel ch...@csamuel.org wrote:
On Sun, 5 Jan 2014 01:25:19 PM Chris Murphy wrote:
Does the Ubuntu 12.03 LTS installer let you create sysroot on a Btrfs raid1
volume?
I doubt it, given the alpha for 14.04 doesn't seem to have the concept yet
it on both disks
which means a single point of failure in which case -o degraded not being
automatic with Btrfs is essentially pointless if we don't have a bootloader. I
also see no way in the UI to even create Btrfs raid of any sort.
Chris Murphy--
To unsubscribe from this list: send the line
to be embarrassed at the answer, but go ahead bite me!
Specify the mount point for the Btrfs file system and it will list all subvols
on that file system.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More
On Jan 8, 2014, at 9:06 PM, Alex a...@bpmit.com wrote:
Chris Murphy lists at colorremedies.com writes:
Specify the mount point for the Btrfs file system and it will list all
subvols on that file system.
Chris Murphy--
Thank you Chris.
When I do that on my version of the 3.12
On Jan 8, 2014, at 11:27 PM, Chris Murphy li...@colorremedies.com wrote:
On Jan 8, 2014, at 9:06 PM, Alex a...@bpmit.com wrote:
Chris Murphy lists at colorremedies.com writes:
Specify the mount point for the Btrfs file system and it will list all
subvols on that file system.
Chris
On Jan 8, 2014, at 11:44 PM, Chris Murphy li...@colorremedies.com wrote:
On Jan 8, 2014, at 11:27 PM, Chris Murphy li...@colorremedies.com wrote:
On Jan 8, 2014, at 9:06 PM, Alex a...@bpmit.com wrote:
Chris Murphy lists at colorremedies.com writes:
Specify the mount point
is a resilient 2 disk failure possible with four disk raid10?
Chris Murphy
--
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
switched to RAID1 as the default mirroring backend)
The problem that in case of mismatches, it's ambiguous which are correct.
Chris Murphy
--
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
a power supply,
controller card, or logic board dying.
Chris Murphy
--
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 whole volume read-only. For production use, going read-only very
well could mean data loss, even while preserving the state of the file system.
Eventually I'd rather see the offending device ejected from the volume, and for
the volume to remain rw,degraded.
Chris Murphy
--
To unsubscribe from
On Jan 9, 2014, at 11:22 AM, Austin S Hemmelgarn ahferro...@gmail.com wrote:
On 2014-01-09 13:08, Chris Murphy wrote:
On Jan 9, 2014, at 5:41 AM, Duncan 1i5t5.dun...@cox.net wrote:
Having checksumming is good, and a second
copy in case one fails the checksum is nice, but what if they BOTH
On Jan 9, 2014, at 12:13 PM, Kyle Gates kylega...@hotmail.com wrote:
On Thu, 9 Jan 2014 11:40:20 -0700 Chris Murphy wrote:
On Jan 9, 2014, at 3:42 AM, Hugo Mills wrote:
On Thu, Jan 09, 2014 at 11:26:26AM +0100, Clemens Eisserer wrote:
Hi,
I am running write-intensive (well sort
btrfs device stats /dev or mountpoint
If there are any errors reported for device stats, what do you get for smartctl
-x /dev/X
Chris Murphy--
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
I shrink the FS to the correct size right now, ensuring that I
really shrink it to the exact LV size?
Right now it's a broken file system, just recreate it.
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
is
all that's needed to locate /boot/grub/ where even more modules can be
arbitrarily loaded, as well as grub.cfg. At this point the kernel and initramfs
could be anywhere, located, and booted.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
/mapper/vg-lv
That's also a reasonable.
Chris Murphy--
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 be explained better,
including the exact commands you used.
Chris Murphy
--
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
fstab to
use fs UUID from blkid.
In the meantime what do you get for :
btrfs fi show
cat /proc/self/mountinfo | grep btrfs
Chris Murphy--
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
are mounted rather than prior ones.
Chris Murphy
--
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
for this volume:
btrfs fi show
btrfs fi df mountpoint
dmesg
smartctl -x dev
I had to unmount it to run btrfsck, but because it fails to repair my
disk, I cannot mount it any more.
Try to mount with -o clear_cache.
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs
for it or you can attach it to a
kernel.org bug report.
Chris Murphy--
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 Jan 13, 2014, at 11:03 PM, Duncan 1i5t5.dun...@cox.net wrote:
Chris Murphy posted on Mon, 13 Jan 2014 17:40:33 -0700 as excerpted:
If you decide to backup, reformat, restore, then first I suggest
btrfs-image -c 9-t 4 /dev/sdX /mnt/pathtoanothervolume+filename
You can keep it handy
On Jan 14, 2014, at 2:30 AM, Duncan 1i5t5.dun...@cox.net wrote:
I wonder if it compresses?
-c 9 is max compression although I don't know what algorithm btrfs-image uses
off hand. If I use xz on it, 193MB becomes 192MB.
Chris Murphy
--
To unsubscribe from this list: send the line
be clearable, but I'd rather not screw up a
drive I like.)
Chris Murphy
--
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
so then you need exception code if you don't want that behavior. I think
it's trouble.
Chris Murphy
--
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 be configuring SMART at all.
Chris Murphy
--
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
combination of the current attributes.
So there's a really good chance the drive will fail without warning. This study
doesn't report on the accuracy of the health self-assessment, i.e. the
PASS/FAIL state for the drive.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux
On Jan 14, 2014, at 2:19 PM, Roman Mamedov r...@romanrm.net wrote:
On Tue, 14 Jan 2014 14:05:11 -0700
Chris Murphy li...@colorremedies.com wrote:
On Jan 14, 2014, at 12:37 PM, Roman Mamedov r...@romanrm.net wrote:
I vaguely remember having some drives that were not able to remap
On Jan 14, 2014, at 2:37 PM, Chris Murphy li...@colorremedies.com wrote:
I've seen that happen on OS X Server (client doesn't produce SMART warnings
in user space).
Oops. It does, just not automatically, it seems you have to go look for this in
Disk Utility.
Chris Murphy
--
To unsubscribe
an interesting case because something this broken is inherently valuable,
especially if it was btrfs repair that made it worse.
Chris Murphy
--
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
On Jan 15, 2014, at 9:15 AM, Mitch Harder mitch.har...@sabayonlinux.org wrote:
On Mon, Jan 13, 2014 at 6:37 PM, Chris Murphy li...@colorremedies.com wrote:
On Jan 13, 2014, at 3:58 PM, Holger Brandsmeier brandsme...@gmail.com
wrote:
Currently btrfsck failes to repair my partition, I get
why - can anyone explain?
What kernel version? Can you:
umount
dmesg -n7
mount
And then try to reproduce the behavior and note any kernel messages in dmesg?
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
this on 3.13.0-0.rc8.
Chris Murphy--
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
kernel-3.13.0-0.rc8.git0.1.fc21.x86_64
# btrfs subvol list / -ta
498 56905 FS_TREE/boot
499 57155 FS_TREE/root
500 57175 FS_TREE/home
boot is mounted at /boot
root is mounted at /
home is mounted at /home
ID5 is mounted at
as you'd like with a really nasty example of single-drive failure, that
would likely be livable for me.
It was just one hypothetical scenario, it's not the only one. If it's really
truly seriously being tested, eventually you'll break it.
Chris Murphy--
To unsubscribe from this list: send
failure. Clearly the file system itself is OK due to
metadata raid1.
Chris Murphy--
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 without the
ensuing data loss.
Chris Murphy
--
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
and resulting data
IN THE ABSENCE of protective checksums and cannot help but wonder if THAT is
what the original article is describing.
Does Btrfs (and I'd presume ZFS) raid5/6 checksum both data and parity chunks?
And in the case of raid6 are the two parities separately checksummed?
Chris
30 seconds to recover.
Overwriting slow sectors should fix the problem.
Yes? No? Other?
Chris Murphy--
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
)' failed.
Aborted
This looks like the block in question was deleted, line 3. I'm not sure what
line 4 is suggesting but possibly the replacement failed.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More
On Jan 27, 2014, at 9:08 AM, Calvin Walton calvin.wal...@kepstin.ca wrote:
On Fri, 2014-01-24 at 17:45 -0700, Chris Murphy wrote:
On Jan 20, 2014, at 9:08 AM, George Mitchell geo...@chinilu.com wrote:
After reading the recent posts on this topic I am beginning to think
there is some real
, it shows top level ID with a value other than 5.
Anyway I really don't know what else to call the undeletable first subvolume.
Chris Murphy
--
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
but if the sums
don't match you don't necessarily know what files are affected.
Chris Murphy
--
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 Jan 27, 2014, at 11:50 AM, Hugo Mills h...@carfax.org.uk wrote:
On Mon, Jan 27, 2014 at 11:44:24AM -0700, Chris Murphy wrote:
On Jan 27, 2014, at 6:53 AM, KC impacto...@googlemail.com wrote:
4. If I have a snapshot of /, can I completely erase this partition and
later restore
On Jan 28, 2014, at 12:45 PM, KC impacto...@googlemail.com wrote:
On 27/01/14 19:44, Chris Murphy wrote:
On Jan 27, 2014, at 6:53 AM, KC impacto...@googlemail.com wrote:
3. If I make a snapshot of / and there are some separate partitions mounted
under /mnt/ or /home/, will snapshot skip
.
Chris Murphy
--
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
subvolume indicated by path must be empty before it can be deleted.
-
That's not correct, but maybe the author meant that a subvolume you intend to
delete must not contain another subvolume. A subvolume in another subvolume
will anchor the parent.
Chris Murphy
btrfs device scan --all-devices
btrfs fi show
But now, I can't mount bunkerA degraded,RW because degraded
filesystems are not allowed to be mounted RW (?)
Have you tried? What errors do you get in user space and dmesg?
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe
profile X to profile Y expected to work when the
volume is mounted degraded? If it's not expected to work, or isn't a good idea,
then maybe balance needs to be disabled on degraded mounts?
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message
On Jan 30, 2014, at 10:58 AM, Hugo Mills h...@carfax.org.uk wrote:
On Thu, Jan 30, 2014 at 10:33:21AM -0700, Chris Murphy wrote:
On Jan 29, 2014, at 12:16 PM, Johan Kröckel johan.kroec...@gmail.com wrote:
My situation:
Former btrfs-RAID1 on two luks encrypted partitions (bunkerA
On Jan 30, 2014, at 11:44 AM, Johan Kröckel johan.kroec...@gmail.com wrote:
2014-01-30 Chris Murphy li...@colorremedies.com:
Is this encrypted Btrfs volume used for rootfs? Or is it only for data? If
it's only for data, then make sure the volume (all subvolumes) are umounted,
then mount
all super blocks.
Also fwiw, it's possible to use wipefs -a /dev/sd[abcd] in a single command for
all drives.
Chris Murphy
--
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
says Btrfs: too many missing devices, writeable
remount is not allowed
The patch says remount but your error says mount. I'm not sure you have the
right patch.
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
:
[filesystem] balance start [options] path
With a missing device, presumably this is obvious, but…
Chris Murphy
--
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
readded list
On Jan 30, 2014, at 2:03 PM, KC impacto...@googlemail.com wrote:
On 28/01/14 21:16, Chris Murphy wrote:
You could also rename /home, create a subvolume home within current
subvolume root, then move the files from directory /home_old to the
subvolume /home. Now when you
are, then the
advantage of a subvolume for snapshots is that it can be independently mounted
to provide access to all snapshots within from which to create derivative
snapshots. And it can also have a nosuid or noexec mount option to prevent old
vulnerabilities from being root executable.
Chris
meta data? Or if the working device also has some problem, which depending on
the configuration might implicate a single SATA controller.
Johan, can you post a full dmesg should be posted somewhere? And also smartctl
-x results for the working drive?
Chris Murphy
--
To unsubscribe from
On Jan 30, 2014, at 11:10 PM, Chris Murphy li...@colorremedies.com wrote:
I'm also seeing many Error reading 1647012864000, -1 with different block
addresses (same -1 though), and also 165992304failed to load free space
cache for block group also with different numbers. Maybe hundreds
Use extlinux, variant of syslinux.
Use extlinux, variant of syslinux.
Chris Murphy
haven't tested and . But then also the step where you create this
intermediate snapshot file isn't necessary, just combine the send receive
commands through pipe.
https://btrfs.wiki.kernel.org/index.php/Incremental_Backup
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe
-only
snapshot which will cause a new read-only snapshot to be created with the
incremental data applied to it. The error you're getting sounds like the parent
read-only snapshot isn't available?
Have you tried -vv flag to get more verbose error information when using btrfs
receive?
Chris Murphy
On Feb 3, 2014, at 1:55 PM, Johan Kröckel johan.kroec...@gmail.com wrote:
2014-01-30 Chris Murphy li...@colorremedies.com:
On Jan 30, 2014, at 10:58 AM, Hugo Mills h...@carfax.org.uk wrote:
On Thu, Jan 30, 2014 at 10:33:21AM -0700, Chris Murphy wrote:
You're doing an online conversion
On Feb 3, 2014, at 3:53 PM, Matthew Lai m...@matthewlai.ca wrote:
On 03/02/2014 11:26 AM, Chris Murphy wrote:
On Feb 3, 2014, at 11:19 AM, Matthew Lai m...@matthewlai.ca wrote:
Thanks. I should clarify what I'm trying to do.
I'm trying to use btrfs send for backup, without having another
User has reported a Fedora Rawhide bug that includes a lot of Btrfs messages.
Kernel is 3.14.0-0.rc1.git1.1.fc21.x86_64.
https://bugzilla.redhat.com/show_bug.cgi?id=1062439
A more full dmesg isn't included in the bug report. I haven't hit this
particular bug running the same kernel, but I am
snapshot?
Chris Murphy
--
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 problem more than once either.
Chris Murphy
--
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
of whether or not
files can be copied.
Chris Murphy--
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
.
Chris Murphy--
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 Feb 7, 2014, at 2:07 PM, Kai Krakow hurikhan77+bt...@gmail.com wrote:
Chris Murphy li...@colorremedies.com schrieb:
If the database/virtual machine/whatever is crash safe, then the
atomic state that a snapshot grabs will be useful.
How fast is this state fixed on disk from the time
a path to subvolume that starts
with the mount point.
Chris Murphy--
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
or disk attribute.
Chris Murphy
--
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 Feb 8, 2014, at 7:21 PM, Chris Murphy li...@colorremedies.com wrote:
we don't have a top level switch for variable raid on a volume yet
This isn't good wording. We don't have a controllable way to set variable raid
levels. The interrupted convert model I'd consider not controllable
Chris Murphy--
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
and continue to work, I don't see how it can depend on swap partitions. It's
fine to create them, but just realize if they're actually being used and the
underlying physical device dies, the kernel isn't going to like it.
A possible work around is using an md raid1 partition as swap.
Chris Murphy
601 - 700 of 2056 matches
Mail list logo
