For modern filesystems such as btrfs, t/p/e size level operations
are common.
add size unit t/p/e parsing to memparse
Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com
---
changelog
v1-v2: replace kilobyte with kibibyte, and others
---
lib/cmdline.c | 25 -
1
To compress a small file range(=blocksize) that is not
an inline extent can not save disk space at all. skip it can
save us some cpu time.
This patch can also fix wrong setting nocompression flag for
inode, say a case when @total_in is 4096, and then we get
@total_compressed 52,because we do
btrfs resize now support size unit parse of k/m/g/t/p/e in kernel space,
adopt the changes in userspace manpage.
Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com
---
changelog
v1-v2: replace kilobyte with kibibyte, and others
---
cmds-filesystem.c | 3 ++-
man/btrfs.8.in| 9
Steps to reproduce:
# mkfs.btrfs -f /dev/sda[8-11] -m raid5 -d raid5
# mount /dev/sda8 /mnt
# btrfs scrub start -BR /mnt
# echo $? --unverified errors make return value be 3
This is because we don't setup right mapping between physical
and logical address for raid56, which makes checksum
Apologies if this is known, but I've been lurking a while on the list and
not seen anything similar - and I'm running out of ideas on what to do next
to debug it.
Small HP microserver box, running Debian, EXT4 system disk plus 4 disk BTRFS
array shared over NFS (nfs-kernel-server) and SMB - the
Hi Linus,
We still have some corruption fixes and other patches coming in for the
merge window, but this batch is tested and ready to go.
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git master
This is a pretty long stream of bug fixes and performance
I'm currently considering to use SELinux on an existing system with
btrfs filesystems. This would be my first with SELinux and I wouldn't
expect everything to go smoothly. I'm already aware that SELinux's
automatic labelling of files is not aware of subvolumes[*]. I already
have quite a few
I'd actually put more faith in the btrfs balance command...
Btrfs scrub is another alternative
I suppose, then, that my ultimate plan of action is thus:
* Back up important data.
* Give `btrfs scrub' a try.
* Give `btrfs balance' a try.
* Rebuild the file system if necessary.
On Tue, 1 Apr 2014 07:15:47 +0800, Shilong Wang wrote:
hello, recently, i was working on btrfsck repair. i post some
patches to make btrfsck to rebuild extent tree with snapshots.
you can pull code from david latest branch and have a try with
btrfsck --init-extent-tree.
Fortunately, the
This implements the tmpfile callback of struct inode_operations, introduced
in the linux kernel 3.11 [1], and implemented already by some filesystems.
Signed-off-by: Filipe David Borba Manana fdman...@gmail.com
---
fs/btrfs/inode.c | 120 +--
1
Hi Chris and Josef,
Below is a lockdep spew I have on a local VM running Linus' tree as of
this afternoon. The specific git commit is v3.14-751-g683b6c6f82a6.
I don't believe any btrfs commits have been merged for 3.15 in this
kernel. The only related commits seem to be the merge of Ingo's
On 04/01/2014 10:25 AM, Chris Mason wrote:
Hi Linus,
We still have some corruption fixes and other patches coming in for the
merge window, but this batch is tested and ready to go.
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git master
Tsutomu noticed
Hello Michael,
On 04/02/2014 03:26 AM, Michael Witten wrote:
On Tue, 1 Apr 2014 07:15:47 +0800, Shilong Wang wrote:
hello, recently, i was working on btrfsck repair. i post some
patches to make btrfsck to rebuild extent tree with snapshots.
you can pull code from david latest branch and have
13 matches
Mail list logo