Now, my questions:
- what do both 104882176 104882176 numbers represent?
- how can I verify the quota assigned to any given subvolume? I've assigned 200
MB, but how can I verify that number?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe
or
not.
The second number shows the amount of data that is unique to this
subvolume and not shared with others, i.e. the amount of space
that will get freed if you delete this subvolume.
Both numbers are bytes, correct?
--
Tomasz Chmielewski
htp://wpkg.org
--
To unsubscribe from this list: send the line
] device label btrfs2 devid 1 transid 7 /dev/sdc1
[ 173.689393] btrfs: disk space caching is enabled
[ 173.690195] btrfs: failed to read the system array on sdc1
[ 173.796816] btrfs: open_ctree failed
Is it expected behaviour that the fs is mountable only once?
--
Tomasz Chmielewski
http
, the data would be compressed with zlib
Would this work as above, or do I have to copy the data out and back to
convert from lzo compression to zlib compression?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
/0x43
Jul 2 21:43:27 bkp010 kernel: [ 696.786331] ---[ end trace 5bc755b97545ce9d
]---
--
Tomasz Chmielewski
http://wpkg.org
--
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
e5
[18483.578527] RIP [a0734e98] __add_tree_block+0x11b/0x12c [btrfs]
[18483.578588] RSP 8802ceb27a28
[18483.578921] ---[ end trace 5fbd1b64c8886e51 ]---
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
: 169513
Dirty: 21024 kB
Removed files: 171877
Dirty: 1936 kB
Removed files: 95442
Dirty: 7780 kB
So it looks like removing files with btrfs needs much more metadata
updates?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from
drawback.
--
Tomasz Chmielewski
http://wpkg.org
--
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
/1177 4096 4096
0/1178 4096 4096
# btrfs qgroup assign 1177 1178 /mnt/lx2
ERROR: bad relation requested '/mnt/lx2'
Could anyone give examples of proper usage of this feature?
This is Linux 3.10.
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe
/1181 16112013312 -22184235008
0/1268 38296248320 0
0/1269 616386560 0
0/1270 4096 4096
0/1271 4096 4096
--
Tomasz Chmielewski
http://wpkg.org
--
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
, thanks.
And is it possible (i.e. at some later point) to verify that 1177, 1178
were assigned to 1/1 (or in general, what is assigned to 1/1)?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
.
--
Tomasz Chmielewski
http://wpkg.org
--
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
-x 1 root staff 1.5M Jul 31 04:30 /usr/local/bin/btrfs
# date
Wed Jul 31 04:33:59 UTC 2013
git log is quite old, too (last change from Thu Nov 8 17:54:13 2012 +0800).
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
?
--
Tomasz Chmielewski
http://wpkg.org
--
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
(device sdb5):
failed to load free space cache for block group 3835502264320
This is running 3.10.
--
Tomasz Chmielewski
http://wpkg.org
--
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 Wed, 31 Jul 2013 14:41:28 +0700
Tomasz Chmielewski man...@wpkg.org wrote:
I'm getting ERROR: quota command failed: Invalid argument when
trying to run btrfs quota rescan - is it expected?
root@bkp010 ~ # btrfs quota rescan /mnt/lxc1
ERROR: quota command failed: Invalid argument
root
: [1589736.946938] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
Aug 2 10:23:11 mach-5 kernel: [1589736.947039] sd 1:0:0:0: [sdb] CDB:
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
0001
--
Tomasz Chmielewski
http://wpkg.org
--
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
4096
0/1336 38598545408 4096
0/1337 631840768 4096
0/1338 631840768 4096
1/1 375578464256 375578464256
2/1 -4096 22732800
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More
On Tue, 06 Aug 2013 07:24:26 +0200
Arne Jansen sensi...@gmx.net wrote:
On 05.08.2013 18:35, Tomasz Chmielewski wrote:
I am trying to use qgroups
functionality with a basic random-write workload, it constantly
keeps leaking memory within few minutes of IO, there is either
out-of-memory
On Wed, 7 Aug 2013 00:42:27 +0800
Tomasz Chmielewski man...@wpkg.org wrote:
What do I have to do to reproduce it here? How do you generate the
load? What is the disk setup, what the qgroups setup?
Unfortunately I don't have a way to reproduce, as the issue
happened to me only once.
I
[137328.096785] RIP [a07212ae] btrfs_clone_extent_buffer+0x5b/0xc3
[btrfs]
[137328.096877] RSP 8801a293d888
[137328.097184] ---[ end trace 64a3e554b4aa9a11 ]---
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
operations on this particular btrfs filesystem
(there was another btrfs filesystem mounted on the same server, using
different drives / mount points, and it was still working fine).
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
qgroup show /mnt/lxc1 | grep 4494
0/4494 839516160 -69632
qgroup 4494 is not used by any subvolume:
# btrfs sub list /mnt/lxc1 | grep 4494
I did run btrfs quota rescan for this filesystem, hoping it will fix
the problem, but it didn't.
Any advice?
--
Tomasz Chmielewski
http://wpkg.org
/src/qgroup/btrfs-progs/btrfs qgroup show /mnt/lxc1 | grep 4494
0/4494 839516160 18446744073709481984
# btrfs qgroup show /mnt/lxc1 | grep 4494
0/4494 839516160 -69632
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
, thanks a lot!
--
Tomasz Chmielewski
http://wpkg.org
--
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
.
Neither worked, same error.
Anything else I can try?
--
Tomasz Chmielewski
http://wpkg.org
--
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 trick, thanks.
--
Tomasz Chmielewski
http://wpkg.org
--
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
45 08 4c 89 28 e9 aa 00 00 00 a8 10
75 02 0f 0b 83 e0 01 41 39 c4 74 02 0f 0b 45 85 e4 75 32 49 8b 70 18
[ 1488.567049] RIP [a035f729] build_backref_tree+0xb10/0xe91
[btrfs]
[ 1488.567207] RSP 8807f9e23928
[ 1488.567325] ---[ end trace 1c4992d3332e9f0f ]---
--
Tomasz Chmielewski
devid3 size 2.56TB used 1.19TB path /dev/sdb4
devid4 size 2.56TB used 1.19TB path /dev/sda4
Btrfs v0.20-rc1-324-g650e656
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
= 32338688kB
[1878432.681992] Total swap = 33553332kB
[1878432.762593] 8388095 pages RAM
[1878432.762659] 171943 pages reserved
[1878432.762716] 4144353 pages shared
[1878432.762764] 3906447 pages non-shared
[1878432.762841] btrfs: qgroup scan failed with -12
--
Tomasz Chmielewski
--
To unsubscribe
, my system was hanging regularly, every few days.
I've disabled BackupPC and I'm running rsync + btrfs snapshot now - no
hang since then (at least till now). Could be coincidence, but who
knows.
[1] http://backuppc.sourceforge.net
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from
] ---[ end trace 00035cab7b970765
]---
--
Tomasz Chmielewski
http://wpkg.org
--
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
is (will be, when it's stable) ready for the future storage.
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Zheng Yan schrieb:
Tomasz Chmielewski wrote:
At the beginning of August, Mikulas Patocka posted to linux-kernel
mailing list about adding snapshot merging to LVM[1].
Basicaly, snapshot merging means that it is possible to turn a snapshot
back into its origin.
Using LVM, however, means
i.e. for /boot, doesn't it?
--
Tomasz Chmielewski
http://wpkg.org
--
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 wouldn't make more data loss than necessary
- taking snapshots of individual files (file images on SAN) is not
possible with btrfs? Probably they would have to be placed in separate
directories first to make snapshots - some minor manageability issue
--
Tomasz Chmielewski
http://wpkg.org
- sure.
--
Tomasz Chmielewski
http://wpkg.org
--
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
more than 33% of deduped data
running a productive set of VMs.
Did you just compare checksums, or did you also compare the data bit
after bit if the checksums matched?
--
Tomasz Chmielewski
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
to be able to
track real world data on those,
See here (The hashing function):
http://backuppc.sourceforge.net/faq/BackupPC.html#some_design_issues
It's not real world data, but it gives some overview which applies here.
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send
00 55 89 e5 8d 50 18 f0 ff 0a 0f 94 c1 84 c9 75
08 5d c3 8d b6 00 00 00 00 e8 13 fe
EIP: [c01b5f36] fput+0x6/0x30 SS:ESP 0068:c4fd3e70
CR2: ffcd
---[ end trace 86b77908c796fc8f ]---
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe
Chris Mason wrote:
On Tue, May 26, 2009 at 08:27:28AM +0200, Tomasz Chmielewski wrote:
I converted an ext4 filesystem with btrfs-convert, mounted it, and wanted to do
lzop -d
The result was an immediate Oops (btrfs is on LVM, on dm-crypt, on /dev/sdb
which is USB-connected).
mini-904
Tomasz Chmielewski wrote:
Pid: 11454, comm: lzop Not tainted (2.6.30-0.rc7.1mdv #1) MS-6728
Does this kernel have any extra patches in it?
It's a distribution kernel with this description: NOTE: This kernel has
no patches and no third-party drivers.
So there shouldn't be any extra patches
Tomasz Chmielewski wrote:
Tomasz Chmielewski wrote:
Pid: 11454, comm: lzop Not tainted (2.6.30-0.rc7.1mdv #1) MS-6728
Does this kernel have any extra patches in it?
It's a distribution kernel with this description: NOTE: This kernel
has no patches and no third-party drivers.
So
with defragmentation? One
excludes the other to some extent.
--
Tomasz Chmielewski
http://wpkg.org
--
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
needed, deduplicate blocks which have
more copies, and allow to overwrite them with data.
Perhaps complicated though.
--
Tomasz Chmielewski
--
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
= 22 ()
Anything interesting in dmesg?
--
Tomasz Chmielewski
http://wpkg.org
--
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 Mason wrote:
On Fri, 2009-04-24 at 01:34 +0200, Tomasz Chmielewski wrote:
Chris Mason schrieb:
However, with btrfs, I'm not sure about:
- what happens if SAN machine crashes while the iSCSI file images were
being written to; with LVM and its block devices, I'm somehow more
confident
: Operation not supported while setting flags on disk.img
--
Tomasz Chmielewski
http://wpkg.org
--
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
00 00 00 0f 18 08 49 8d 84 24
b0 00 00 00 49 39 c7 75 27 4c 89 f7 e8 2a 79 bd df 0f 0b eb fe be 5c 0b 00 00
48 c7 c7 9b d2 6e a0 e8 05 5d bb df
RIP [a06a5426] __btrfs_reserve_extent+0x296/0x310 [btrfs]
RSP 8800bb441808
---[ end trace a51370eaca1eb6d6 ]---
--
Tomasz Chmielewski
http
David Woodhouse wrote:
On Mon, 2009-07-13 at 12:28 +0200, Tomasz Chmielewski wrote:
How do I replace failed disks in RAID-1 mode?
I don't think you can. In theory you can remove the broken one, and you
can add a _new_ empty one -- I say 'in theory' because you seem to have
demonstrated both
) for btrfs until
it stabilizes.
But certainly not for md RAID-1. _If_ it did work for you, you would
have to take the whole array down as dd works, which is not good. md
provides its own tools (mdadm) to replace/rebuild the RAID.
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from
Chris Mason wrote:
On Mon, Jul 13, 2009 at 12:28:09PM +0200, Tomasz Chmielewski wrote:
How do I replace failed disks in RAID-1 mode?
I followed the
http://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices, but
it triggered a kernel BUG (using 2.6.30.1 kernel):
# mount -o
it was the case about a year ago, could
be that the things improved).
[1] http://stgt.berlios.de
[2] http://scst.sf.net
--
Tomasz Chmielewski
http://wpkg.org
--
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
in the meantime.
But sure, it's a change.
--
Tomasz Chmielewski
http://wpkg.org
--
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
/sdb4
# mount /dev/sda4 /mnt/btrfs/
Does it make sense?
It behaved like this also with some earlier kernels.
--
Tomasz Chmielewski
http://wpkg.org
--
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
longer term, doing btrfsctl -a before mounting a (RAID)
btrfs filesystem shouldn't be needed, or?
--
Tomasz Chmielewski
http://wpkg.org
--
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
,bar)
--
Tomasz Chmielewski
http://wpkg.org
--
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 this limit, it's ridiculously small.
Of course, not necessarily right now, but when you introduce some other
changes needing disk format change, please think of removing the hard
link limit as well.
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line
/index2/shared_cpu_map
Message from sysl...@dom at Mon Oct 12 22:31:49 2009 ...
dom klogd: [ 9657.948574] Stack:
Message from sysl...@dom at Mon Oct 12 22:31:49 2009 ...
dom klogd: [ 9657.948589] Call Trace:
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line
://scst.sf.net).
--
Tomasz Chmielewski
http://wpkg.org
--
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
(perhaps, with a reboot in between).
If it's possible, what would be the steps/commands?
--
Tomasz Chmielewski
http://wpkg.org
--
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
without adding any subvol=newsnap mount arguments
Correct me if I'm wrong.
--
Tomasz Chmielewski
http://wpkg.org
--
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
. For
example, while it copies/updates a file, we will have:
original_file.bin
.temporary_random_name
Later, original_file.bin would be removed, and .temporary_random_name
would be renamed to original_file.bin. Here goes away any deduplication
we had so far, we have to start the IO over again.
--
Tomasz
on 3260289024 wanted 169686 found 169685
parent transid verify failed on 3260289024 wanted 169686 found 169685
btrfs: open_ctree failed
Tried to get that mounted with 2.6.35 and 2.6.37, without success.
Is there a way to fix it?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from
1948176384 bytes used err is 1
total csum bytes: 1739600
total tree bytes: 166825984
total fs tree bytes: 150220800
btree space waste bytes: 43746814
file data blocks allocated: 7267450880
referenced 5718896640
Btrfs Btrfs v0.19
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from
*
$ grep -r selects-super *
I used:
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs-unstable.git
next
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More
and was usable.
--
Tomasz Chmielewski
http://wpkg.org
--
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 fix was
pushed yet or not?
The filesystem should have plenty of free space free:
FilesystemSize Used Avail Use% Mounted on
/dev/sdb4 336G 156G 179G 47% /srv
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux
,compress-force=lzo,device=/dev/sdc,device=/dev/sdd)
I don't need to recover the file, just trying to signal something doesn't work
well here!
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
is 2.6.39, device is relatively large.
It is *probably* related to compression used (compress-force - disabled
the option, and didn't see out of space since).
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
0.00 88.27
Device:tpsMB_read/sMB_wrtn/sMB_readMB_wrtn
sdb4127.37 0.92 1.94 94207 199369
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message
On 22.05.2011 11:34, Stephane Chazelas wrote:
2011-05-21 14:58:21 +0200, Tomasz Chmielewski:
I have a btrfs filesystem (2.6.39) which is mounted, but otherwise, not used:
# lsof -n|grep /mnt/btrfs
processes with open fds are one thing. You could also have loop
devices setup
/16384/16516_fsm'
removed `postgresql-noindex/postgresql/8.4/main/base/16384/16521'
This is a snapshot of a different directory (with some changes).
Is it expected? I'm running 2.6.39.1 kernel.
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux
fails with No space left on the
device, while there is ~70 GB free on btrfs filesystem; and copying
some other files, with similar or bigger size, succeeds).
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message
This way, when the writes are CPU-bound, I'm able to fully fill the
btrfs filesystem (~8 MB/s):
# dd if=/dev/urandom of=/mnt/btrfs/bigfile
Delayed allocation?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message
48 63 d3 48 8d 75 bf 48 6b d2 19 b9 11 00 00
[525983.970116] RIP [a02a8361] btrfs_set_item_key_safe+0xb2/0x119
[btrfs]
[525983.970237] RSP 8805eb9f9b18
[525983.970581] ---[ end trace 40b604c8c92dba0d ]---
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list
with autodefrag
mount option disabled.
--
Tomasz Chmielewski
http://wpkg.org
On Sun, 23 Feb 2014 12:25:28 +0100
Tomasz Chmielewski t...@virtall.com wrote:
Got this with 3.14-rc3:
[525983.966567] [ cut here ]
[525983.966645] kernel BUG at fs/btrfs/ctree.c:3215
880601fb9b18
[377944.910260] ---[ end trace e209399cfd0911cd ]---
--
Tomasz Chmielewski
http://wpkg.org
--
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
: [195837.281367] BTRFS: bdev /dev/sdd1 errs: wr
113630, rd 443, flush 0, corrupt 0, gen 0
--
Tomasz Chmielewski
http://wpkg.org
--
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
00 01 00 00 48 89 e5 48 8b 90 80 02
[ 581.341762] RIP [8111f33b] bio_get_nr_vecs+0x0/0x38
[ 581.341870] RSP 8807e770b7d0
[ 581.341944] CR2: 0098
[ 581.342019] ---[ end trace 36d74486b120a454 ]---
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list
?
I'm not sure, sorry.
It's just a routine cronjob:
- rsync - snapshot - remove old snapshots
--
Tomasz Chmielewski
http://wpkg.org
--
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
snapshotting), so I've downgraded to 3.14.2 (no
hanging so far).
--
Tomasz Chmielewski
http://wpkg.org
--
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
devices at the same time.
Also, what happens when the system crashes, and one drive has several
hundred megabytes data more than the other one?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord
removing (many) snapshots.
Not sure if that's optimal behaviour.
--
Tomasz Chmielewski
http://wpkg.org
--
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
with -o degraded option.
However it hangs here...
--
Tomasz Chmielewski
http://wpkg.org
--
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 write
to the replaced device only).
Of course, other factors such as the amount of data or disk IO usage
during rebuild apply.
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More
, but then, it's not possible to add a
disk and recover to a functioning RAID-1.
Also, when I try to remount rw, the mount command hangs as well.
Is there anything else I can try?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body
b3b58e5cee91bc55 ]---
--
Tomasz Chmielewski
http://www.sslrack.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
will be used.
Do you want to continue [Y/n]? n
Abort.
--
Tomasz Chmielewski
http://www.sslrack.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
[ 1704.294757] btrfs: free space inode generation (0) did not match free space
cache generation (22503)
[ 1704.294761] btrfs: failed to load free space cache for block group
243231883264
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs
to write/read? That leads to the second question: How can
I debug file system activity in inotify style?
There was once a similar thread about this issue; unfortunately, without
any constructive answers:
http://thread.gmane.org/gmane.comp.file-systems.btrfs/10840
--
Tomasz Chmielewski
http
anywhere where ext3/ext4 would just silently ignore fsync?
--
Tomasz Chmielewski
http://wpkg.org
--
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
IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
fs created label (null) on /dev/md0
nodesize 4096 leafsize 4096 sectorsize 4096 size 9.76GB
Btrfs Btrfs v0.19
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux
ret -1 errno 28
total 1 failures
Some files fail to defragment like this; some are defragmented correctly.
Why does it fail?
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More
7c45187572db04d2 ]---
--
Tomasz Chmielewski
http://wpkg.org
--
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 04.10.2010 16:24, Felix Blanke wrote:
Hi,
that issue is allready reported to this mailinglist and there is a longer
conversation about it.
Indeed:
http://thread.gmane.org/gmane.linux.kernel/1039525
--
Tomasz Chmielewski
http://wpkg.org
--
To unsubscribe from this list: send the line
with no space left.
--
Tomasz Chmielewski
http://wpkg.org
--
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
).
--
Tomasz Chmielewski
http://wpkg.org
--
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
1 - 100 of 258 matches
Mail list logo
