Dear list members,
I upgraded to 3.13-rc5 kernel and started to defrag my whole file system with
the following commands:
cd /
for i in */*; do if [[ $i != windows* ]]; then echo --$i--; btrfs
fi defrag -clzo -r $i; fi; done 21 | tee /root/defrag
After 10 or 15 seconds my computer
Chris Murphy posted on Sat, 28 Dec 2013 16:11:37 -0700 as excerpted:
I am slightly bugged about a 16MB file having nearly 2000 extents,
basically it's being turned into a bunch of 8KB fragments. I know
nothing of the pros and cons of how systemd is writing journals, but
they don't seem very
@full is not protected within global_rsv.lock, so we may think global_rsv
is already full but in fact it's not, so we miss the opportunity to return
free space to global_rsv directly when we release other block_rsvs.
Signed-off-by: Liu Bo bo.li@oracle.com
---
fs/btrfs/extent-tree.c | 2 +-
1
We don't have to keep subvolume's block_rsv during transaction commit,
and within transaction commit, we may also need the free space reclaimed
from this block_rsv to process delayed refs.
Signed-off-by: Liu Bo bo.li@oracle.com
---
fs/btrfs/ioctl.c | 7 ---
1 file changed, 4
Hello list!
I'm planning to buy a small SSD (around 60GB) and use it for bcache in front
of my 3x 1TB HDD btrfs setup (mraid1+draid0) using write-back caching. Btrfs
is my root device, thus the system must be able to boot from bcache using
init ramdisk. My /boot is a separate filesystem
On Dec 29, 2013, at 5:39 AM, Duncan 1i5t5.dun...@cox.net wrote:
Yes, it does turn off checksumming as well as COW, but given the write-
into scenario, that's actually best anyway, because otherwise btrfs has
to keep updating the checksums
On second thought, I'm less concerned with bitrot
On Dec 29, 2013, at 2:11 PM, Kai Krakow hurikhan77+bt...@gmail.com wrote:
* How stable is it? I've read about some csum errors lately…
Seems like bcache devs are still looking into the recent btrfs csum issues.
* I want to migrate my current storage to bcache without replaying a backup.
Chris Murphy li...@colorremedies.com schrieb:
I think most of these questions are better suited for the bcache list.
Ah yes, you are true. I will repost the non-btrfs related questions to the
bcache list. But actually I am most interested in using bcache together
btrfs, so getting a general
On Dec 29, 2013, at 6:22 PM, Kai Krakow hurikhan77+bt...@gmail.com wrote:
So you are saying that data
may not be fully written to SSD although the kernel thinks so?
Drives shouldn't lie when asked to flush to disk, but they do. Older article
about this at lwn is a decent primer on the
Kai Krakow posted on Sun, 29 Dec 2013 22:11:16 +0100 as excerpted:
Hello list!
I'm planning to buy a small SSD (around 60GB) and use it for bcache in
front of my 3x 1TB HDD btrfs setup (mraid1+draid0) using write-back
caching. Btrfs is my root device, thus the system must be able to boot
So after transaction is aborted, we need to cleanup inode resources by
calling btrfs_invalidate_inodes(), and btrfs_invalidate_inodes() hopes
roots' refs to be zero in old times and sets a WARN_ON(), however, this
is not always true within cleaning up transaction, so WARN_ON_ONCE() is
better, and
11 matches
Mail list logo
