a gb of full.
Both are good rules of thumb. Thanks.
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
shows.
Is this reproducible with either kernel-3.7.2-201.fc18 or
kernel-3.8.0-0.rc3.git0.1.fc19? Both are in koji.
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
starts allocating more chunks to the
device(s) that have space. This means there's a distinction in behavior between
md's level 'raid10' and separately creating a stripe of mirrors, i.e. first
creating raid1 arrays, then striping them with raid0.
Chris Murphy--
To unsubscribe from this list: send
-1 is the same size as the LV?
You say the btrfs volume on LV is on dm-1 which means they're all the same
size, obviating the need for LVM in this case entirely.
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
sooner than you'd otherwise
expect.
When this problem is happening, with the low bandwidth writing, can you hear
disk chatter? On all of the drives at the same time or just one or two at a
time?
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
On Jan 30, 2013, at 9:10 PM, Roman Mamedov r...@romanrm.ru wrote:
How about btrfs check?
For that matter, separate out check and repair. Is there a potential for a
btrfsck repair to make things worse? And if so, could this be determined with a
check?
Chris Murphy--
To unsubscribe from
see why striping is considered fragmentation.
To change the profile for the volume, you use -dconvert and/or -mconvert with a
rebalance operation.
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
that this is non-rotating
media, it should have mounted it with the ssd option. The other mount option
possible, which is manually set (and unsets ssd) is ssd_spread.
https://btrfs.wiki.kernel.org/index.php/FAQ#What_is_the_difference_between_mount_-o_ssd_and_mount_-o_ssd_spread.3F
Chris Murphy
is to not partition your devices at all if
you're concerned about efficiency. Just use the whole drive as the 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
at the moment. But it could be other things too. What
kernel version?
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
from the kernel. As this is hdi, I'm wondering
how many drives are connected, and if this could be power induced rather than
just cable induced. Once that's solved, you should do a scrub, rather than a
rebalance.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux
that mkfs.xfs doesn't nerf a file system
without the use of -f; even an existing XFS file system. Considering most data
loss is user induced, I'd appreciate it if other file systems's tools weren't
so easily made belligerent by (hopefully temporarily) confused apes wearing
pants.
Chris Murphy
in dmesg.
Also, is a virtual machine being used in any of this, either as host or guest?
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
of the md write-intent bitmap, reducing the time
to catch the drive up, avoiding a full scrub?
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 how btrfs should behave in such a case. md would
have tossed the drive and as far as I know doesn't automatically readd it if it
reappears as either the same or a different block device. And when the user
uses --re-add there's a resync.
Chris Murphy--
To unsubscribe from this list: send
different disk, the first partition is
btrfs, mounted as /home. So long as the contents are user folders, i.e. the
same thing found in sde2 subvol @home, then it's functionally the same as what
you had before.
Also, btrfs doesn't need fs_passno set.
Chris Murphy--
To unsubscribe from this list
!
kernel 3.0.0 is positively ancient in btrfs terms. I defer to others on what
kernel should be used at the present time for an Ubuntu server, but I know they
have much newer kernels than 3.0.0 available.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs
for the OP's use case is encryptfs which encrypts above
btrfs. The file contents are encrypted, but the file names and file system
itself (and metadata) are not. In this case, deletion is functionally
equivalent to having filled the blocks with random data (short of the DEK
escaping into the wild).
Chris
not in use. But there's no requirement for what kind of data is used
for overwriting.
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 overwhelming concern is someone gaining physical access to the
drive: theft of a laptop, or disposal of a dead drive (for which ATA security
erase unit commands aren't going to work). And for that encryption is quite
useful and important.
Chris Murphy--
To unsubscribe from this list: send the line
On Mar 19, 2013, at 3:06 AM, David Sterba dste...@suse.cz wrote:
On Mon, Mar 18, 2013 at 09:18:28PM -0600, Chris Murphy wrote:
I'm not finding a reference to secure erase trim. In any case I
wouldn't expect it to differ from trim.
There's a 'secure discard' trim command in linux,
http
these files. So, the only way
to solve these problems is to replace the filesystem.
The storage media isn't reliable. Replacing the file system eventually will get
you right back where you are now, except in a case of multiple devices with a
reliable 2nd device.
Chris Murphy--
To unsubscribe from
On Mar 20, 2013, at 1:24 PM, Roman Mamedov r...@romanrm.ru wrote:
On Wed, 20 Mar 2013 12:19:18 -0600
Chris Murphy li...@colorremedies.com wrote:
195 Hardware_ECC_Recovered 0x001a 057 055 000Old_age Always
- 63508940
With such high ECC recovered events, I
On Mar 21, 2013, at 2:57 AM, Frédéric COIFFIER frederic.coiff...@free.fr
wrote:
Hi Roman,
Le jeudi 21 mars 2013 01:24:14 Roman Mamedov a écrit :
On Wed, 20 Mar 2013 12:19:18 -0600
Chris Murphy li...@colorremedies.com wrote:
195 Hardware_ECC_Recovered 0x001a 057 055 000
kernels.
Is this expected?
dmesg reports:
[ 300.014764] btrfs: disk space caching is enabled
[ 300.024137] BTRFS: couldn't mount because of unsupported optional features
(40).
[ 300.034148] btrfs: open_ctree failed
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux
On Mar 29, 2013, at 12:04 AM, cwillu cwi...@cwillu.com wrote:
On Thu, Mar 28, 2013 at 11:41 PM, Chris Murphy li...@colorremedies.com
wrote:
Creating a btrfs file system using
btrfs-progs-0.20.rc1.20130308git704a08c-1.fc19, and either kernel
3.6.10-4.fc18 or 3.9.0-0.rc3.git0.3.fc19, makes
Chris Murphy wrote:
On Mar 29, 2013, at 12:04 AM, cwillu cwi...@cwillu.com wrote:
commit 1a72afaa btrfs-progs: mkfs support for extended inode refs
unconditionally enables extended irefs (which permits more than 4k
links to the same inode). It's the right default imo, but there
probably
On Mar 29, 2013, at 9:42 AM, Mitch Harder mitch.har...@sabayonlinux.org wrote:
On Fri, Mar 29, 2013 at 1:21 AM, Chris Murphy li...@colorremedies.com wrote:
mkfs.btrfs -l 8192 with kernel 3.9.0 creates a file system mountable by
3.9.0 and only 3.9.0 (so far). And while there's no error
by being unable to mount a btrfs
volume. The prospect of a (final release) Fedora 19 created btrfs volume being
totally unreadable by anything less than kernel 3.9.0 is a bit eyebrow raising.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message
for the btrfsck to complete if it is recreating an extents
tree?…
Yes because scrub is online/mounted, and btrfsck is offline/unmounted.
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
referred to here:
https://btrfs.wiki.kernel.org/index.php/Btrfs-image
this will write the file system state minus data, in case a developer wants to
see it at some point. In the meantime you can then blow away the file system
and restore the data to get on with using it.
Chris Murphy
it should always start from top level
regardless of the set-default subvolume, correct? Yet it's behaving relative to
the default subvolume. If I use 'ls (hd0,msdos1)' I'm returned the contents of
the subvolume I've set as default, which explains why bootability is broken.
Chris Murphy--
To unsubscribe
On Oct 14, 2013, at 1:21 PM, Chris Murphy li...@colorremedies.com wrote:
When /boot is on btrfs, and the default subvolume is changed, it makes the
system unbootable. The basic configuration is subvolumes: boot, root, home,
on one btrfs volume single device. The installer doesn't change
On Oct 14, 2013, at 2:29 PM, Josef Bacik jba...@fusionio.com wrote:
On Mon, Oct 14, 2013 at 02:23:58PM -0600, Chris Murphy wrote:
On Oct 14, 2013, at 1:21 PM, Chris Murphy li...@colorremedies.com wrote:
When /boot is on btrfs, and the default subvolume is changed, it makes the
system
the exact same message with a successful mount.
So should the mounting of relative pathnames still work?
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
On Oct 15, 2013, at 1:23 PM, Chris Murphy li...@colorremedies.com wrote:
So should the mounting of relative pathnames still work?
Is it related to fix: [PATCH] Btrfs: use right root when checking for hash
collision
can't move subvols into subvols
http://www.mail-archive.com/linux-btrfs
be angels dancing on headpins territory, but I'm curious if successful
mount is reproducible with either 3.4.66 or 3.9.11. The 3.5 through 3.8 kernels
are neither listed as stable nor longterm.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
On Oct 15, 2013, at 1:23 PM, Chris Murphy li...@colorremedies.com wrote:
After changing the default subvolume, I can't mount a nested subvolume with a
correct relative pathname to the default subvolume; it can only be mounted by
absolute path or subvolid.
Setup:
3.11.4-302.fc20.x86_64
On Oct 15, 2013, at 2:50 PM, David Sterba dste...@suse.cz wrote:
On Tue, Oct 15, 2013 at 01:23:44PM -0600, Chris Murphy wrote:
After changing the default subvolume, I can't mount a nested subvolume
with a correct relative pathname to the default subvolume; it can only
be mounted by absolute
On Oct 15, 2013, at 3:48 PM, David Sterba dste...@suse.cz wrote:
On Tue, Oct 15, 2013 at 02:58:22PM -0600, Chris Murphy wrote:
Looks like this changed with the 3.2 kernel Subvolumes mountable by
full path, I thought that was in addition to relative rather than a
total change in behavior
that prevented moving of subvolumes into subvolumes
(untested if moving subvolumes into folders worked) that was fixed in kernel
3.11.6 so that might be worth a shot.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
On Oct 24, 2013, at 4:46 PM, Karl Kiniger karl.kini...@med.ge.com wrote:
On Thu 131024, Chris Murphy wrote:
dr. 1 chris chris 0 Oct 24 16:15 donotmove
[chris@f20s ~]$ mv donotmove/ Videos/
mv: cannot move ‘donotmove/’ to ‘Videos/donotmove’: Permission denied'
I own
and
fails? What's the exact copy command you're using?
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
mount options, and use the same cp -a
on a 5.3GB file and cannot reproduce your results.
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 Oct 27, 2013, at 3:53 PM, Igor M igor...@gmail.com wrote:
I made some more tests. Disk is 3TB, first cca 225GB is copied without errors.
Then errors 'No space left on device' begins.
Post the full entire dmesg somewhere please. pastebin.com is one option.
Chris Murphy--
To unsubscribe
On Oct 27, 2013, at 4:46 PM, Chris Murphy li...@colorremedies.com wrote:
On Oct 27, 2013, at 3:53 PM, Igor M igor...@gmail.com wrote:
I made some more tests. Disk is 3TB, first cca 225GB is copied without
errors.
Then errors 'No space left on device' begins.
Post the full entire
to a
COMRESET
That's unexpected but I don't know that it's releated. The dmesg doesn't report
any phy issues with the drive. Maybe check syslog or journalctl with a case
insensitive search for phy and see if you find anything.
Chris Murphy
--
To unsubscribe from this list: send the line
for stable to go into
mainline 3.11.6, so somehow it's been missed.
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
in particular /var. It's complicating how the OS is to be put back
together again.
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 the corruption
would be needed and also when trying to mount with the recovery option so it
might be worth:
dmesg
[note the last time entry]
dmesg -n7
btrfs mount -o recovery dev mp
dmesg
report results since the previously noted last time entry
Chris Murphy--
To unsubscribe from this list
On Nov 8, 2013, at 1:13 AM, Hugo Mills h...@carfax.org.uk wrote:
On Thu, Nov 07, 2013 at 10:56:10PM -0700, Chris Murphy wrote:
What's the kernel and btrfs progs version?
I wish the dmesg errors were more explicit about the nature of checksum
errors: do the two metadata checksums mismatch
this rather than distribution convention.
We need some distribution collaboration in this area, or this is going to turn
into an end-user pain point, with multiboot users top on the list of the
injured.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
. And should consider
newschoolers, not just oldschoolers, who will become confused by antiquated
conventions that have little (or no) efficacy.
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
to highly complex and
variable layouts required to support snapshot system rollbacks is what we'll
just have to expect. In which case multiboot on Btrfs is dead in the water.
Each distro would have to have their own volume, not their own subvolumes.
Chris Murphy--
To unsubscribe from this list
for the listed path, and if the top
level is 5, there is no prefix for path, the path is the full path.
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
What's leafsize was used when making the file system? The default is now (as of
yesterday) 16KB to avoid metadata fragmentation.
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 Nov 5, 2013, at 7:34 AM, Hugo Mills h...@carfax.org.uk wrote:
On Tue, Nov 05, 2013 at 07:26:54AM -0700, Chris Murphy wrote:
On Nov 5, 2013, at 5:16 AM, Russell Coker russ...@coker.com.au wrote:
I presume that my filesystem is still corrupt.
I'm the original reporter of the bug
block group
mixing? Try 100GB for each device. Is the problem reproducible?
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
outputs; one for each volume.
Now I get three outputs for the SSD storage volume and SIX outputs for the
out volume.
Is this a bug or a feature? If it is a feature, what is it telling me?
I filed a bug on it.
https://bugzilla.redhat.com/show_bug.cgi?id=1031299
Chris Murphy--
To unsubscribe
unmounted filesystems (and thus the pause), but at least
here, this list is BOTH comprehensive AND avoids dups!
This does show me a single instance of the singular volume I have.
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message
Since qcow2 only supports metadata preallocation, not full preallocation, I'm
wondering if +C on the sparse file is sufficient, or alternatively using
qemu-create -o preallocation=metadata,compat=1.1,lazy_refcounts=on? Or is qcow2
on btrfs just not a good idea?
Chris Murphy--
To unsubscribe
if this is easiest for you fine, but I still think there's at least one bug
somewhere and you shouldn't have to do this.
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
be useful to the btrfs devs about this?
sysrq+w would dump the blockage to kernel messages. Depending on your kernel
you may need to first enable sysrq functions with
echo 1 /proc/sys/kernel/sysrq
then
echo 2 /proc/sysrq-trigger
then
dmesg
Chris Murphy--
To unsubscribe from this list: send
On Nov 18, 2013, at 8:53 PM, Chris Murphy li...@colorremedies.com wrote:
On Nov 18, 2013, at 8:00 PM, Charles Cazabon
charlesc-lists-bt...@pyropus.ca wrote:
This is on x86_64, server-class hardware (ECC memory, etc). I ran a scrub
overnight that reported no errors, and I'll do it again
parity and beyond.
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
drive.) So I think
those companies can develop this otherwise unneeded feature.
n-copies raid1 is a good idea and I think it's being worked on.
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
is
employed).
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
://bugzilla.redhat.com/show_bug.cgi?id=862871
So the question, is there supposed to be (one day) a faux /sbin/fsck.btrfs? Or
should things always check /etc/fstab fs_passno and honor the fact there is
really no such thing?
Thanks,
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux
On Nov 26, 2013, at 5:51 PM, Dave Chinner da...@fromorbit.com wrote:
On Mon, Nov 25, 2013 at 11:40:49PM -0700, Chris Murphy wrote:
Hi,
Is there supposed to be an /sbin/fsck.btrfs? I'm seeing a handful
of threads indicating some idea of having it just do a no-op like
fsck.xfs does
, and, using special GPT
partitiontypeguids, it's automounting swap and /home even if they're not listed
in fstab.)
Any comments on the efficacy of initial ro state when / is on Btrfs?
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
are being copied, even sectors you
probably don't need. So I personally would use rsync or btrfs send, to get the
data off the drive rather than every sector, many of which you don't care about.
Chris Murphy--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message
.
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 9, 2013, at 11:54 AM, Niklas Schnelle niklas.schne...@gmail.com wrote:
On Sat, Dec 7, 2013 at 11:30 PM, Chris Murphy li...@colorremedies.com wrote:
On Dec 7, 2013, at 3:36 AM, Niklas Schnelle niklas.schne...@gmail.com
wrote:
Hi List,
so first the basics. I'm running Arch Linux
On Dec 10, 2013, at 1:31 PM, Imran Geriskovan imran.gerisko...@gmail.com
wrote:
Currently, if you want to protect your data against bit-rot on
a single device you must have 2 btrfs partitions and mount
them as Raid1.
No this also works:
mkfs.btrfs -d dup -m dup -M device
Chris Murphy
documentation also says incurs a performance
hit, although I'm uncertain of the significance.
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
, or triplicate copies.
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
not
present 512byte sectors. And since UEFI bugs are all over the place, I'd kinda
expect booting to work with some firmware and not others. I haven't tested it,
but I'm pretty sure I've read GRUB2 and the kernel are able to boot from 4Kn
drives so long as the firmware can handle it.
Chris
is in the mostly going to cause you problems without it
area). 16 GiB is what we have on the wiki, I think.
Yes, man mkfs.btrfs also doesn't list dup as a possible option for -d.
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
data?
My understanding, which may be wrong, is that the drive only needs power. The
data doesn't need to be re-written.
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
.
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
?
Yes.
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
inconsistent.
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
haven't tried doing it over a network.
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
.
This is a bit of a hijack question, but does kickstart offer a way to mount
Btrfs with compression option?
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
/sysrq.txt
The filesystem have used about 26TB of the available 29TB (real
available data), and some of the files on it are heavily fragmented
(around 100 000 extents at about 25GB)
Please include results from btrfs fi show, and btrfs fi df mp.
Chris Murphy--
To unsubscribe from this list: send
storage won't get this full.
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 the
size of your FS?
Maybe it depends more on the size and fragmentation of the files being access,
and of remaining free space.
Can you do an lsattr on these 25GB files that you say have ~ 100,000 extents?
And what are these files?
Chris Murphy--
To unsubscribe from this list: send the line
On Dec 15, 2013, at 10:40 AM, Gene Czarcinski gczarcin...@gmail.com wrote:
On 12/14/2013 01:43 PM, Chris Murphy wrote:
On Dec 14, 2013, at 2:57 AM, Gene Czarcinski gczarcin...@gmail.com wrote:
Since I run Fedora with anaconda I use kickstart installs and can easily
repeat an install since
to delete
needs to be mounted.
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
: 277
Generation (Gen): 1048
Gen at creation:1048
Parent: 259
Top Level: 259
Flags: -
Snapshot(s):
Chris Murphy
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs
is current.
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
this missing drive message is
about, if you've done a drive replacement and exactly what commands you used to
do that and how long ago.
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 Dec 19, 2013, at 5:06 PM, Chris Kastorff encryp...@gmail.com wrote:
On 12/19/2013 02:21 PM, Chris Murphy wrote:
On Dec 19, 2013, at 2:26 AM, Chris Kastorff encryp...@gmail.com wrote:
btrfs-progs v0.20-rc1-358-g194aa4a-dirty
Most of what you're using is in the kernel so
to go from here, aside from grabbing a compiler and
having at the disk structures myself.
There are some other options but they get progressively and quickly into
possibly making things a lot worse. At a certain point it's an extraction
operation rather than repair and continue.
Chris Murphy
) and is persistent. If I temporarily add mount
option recovery, then they get cleaned up. Expected?
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
://koji.fedoraproject.org/koji/buildinfo?buildID=486644 And also via the
updates-testing repo within a day or two.
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
(at least on btrfs) or maybe systemd
should set xattr +C on /var/log/journal? That does disable checksumming though,
along with data cow.
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
receive.
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
@ list? Or
maybe file it as an RFE against systemd at freedesktop.org?
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
501 - 600 of 2056 matches
Mail list logo
