similar to: Implementing encryption. Any specs?

Hi Thomas, >----Messaggio originale---- >Da: thomas@kupper.org >Data: 22/01/2010 10.48 >A: "Leszek Ciesielski"<skolima@gmail.com> >Cc: "linux-btrfs"<linux-btrfs@vger.kernel.org> >Ogg: Re: mount command not honoring rootflags passed > > >On 22 Jan 2010, at 10:40, Leszek Ciesielski wrote: > >> On Fri, Jan 22, 2010 at 10:30 AM,

HI all, >----Messaggio originale---- >Da: chris.mason@fusionio.com >Data: 20/06/2012 1.49 >A: "H. Peter Anvin"<hpa@zytor.com> >Cc: "linux-btrfs@vger.kernel.org"<linux-btrfs@vger.kernel.org> >Ogg: Re: Subvolumes and /proc/self/mountinfo > >> b. Are there better ways (walking the tree using BTRFS_IOC_TREE_SEARCH?) >> to accomplish

Hey guys, I was trying to build the btrfs modules from btrfs- unstable.git/master against the Ubuntu Karmic 2.6.31 kernel, and get some failures in ref-cache.c: /home/jdong/code/kernel/btrfs-0.17/ref-cache.h:62: error: dereferencing pointer to incomplete type /home/jdong/code/kernel/btrfs-0.17/ref-cache.c: In function ‘btrfs_remove_leaf_refs’:

I made a btrfs on five disks using RAID5 (-d raid5 for mount option). When a power failure occurs, I can not remount btrfs after my system reboots. Dmesg for remount is presented as following: [ 192.713953] bio: create slab <bio-1> at 1 [ 192.716230] Btrfs loaded [ 192.717177] device fsid a0dff7ea-9354-43fd-8516-0e17f370991d devid 1 transid 6 /dev/sdb [ 192.717712] btrfs: disk space

Hi, everyone! mkfs.btrfs just does the following check for sectorsize when we use it to make a btrfs. sectorsize = max(sectorsize, (u32)getpagesize()); Does that mean we can set sectorsize to any number greater than pagesize? If not, I think we should do more check for sectorsize in mkfs.btrfs. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of

It is well documented that btrfs data recovery (after silent corruption) is dependent on the use of btrfs''s own RAID1. However, I''m curious about whether any hardware RAID vendors are contemplating ways to integrate more closely with btrfs, for example, such that when btrfs detects a bad checksum, it would be able to ask the hardware RAID controller to return all alternate

Josef has implemented mixed data/metadata chunks, we must add those chunks'' space just like data chunks. Signed-off-by: Miao Xie <miaox@cn.fujitsu.com> --- fs/btrfs/super.c | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c index 61bd79a..1d21208 100644 --- a/fs/btrfs/super.c +++ b/fs/btrfs/super.c @@ -768,11 +768,10

The condition can be relaxed to accept also 0 which will delete unoccupied chunks and does not need space for the actual data relocation. Until there is an automatic empty chunk reclaim, we can use this as a last resort option under enospc. CC: Ilya Dryomov <idryomov@gmail.com> Signed-off-by: David Sterba <dsterba@suse.cz> --- Also needs progs update, but is not required for the

Dear list members, When I tried to recover my partition from the space cache bug (see http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg24360.html ), I issued the command `mount -o clear_cache -t btrfs /dev/sda7 /aaa/aaa`. After 10 minutes the mount command segfaulted. I cloned the latest btrfs-progs from Josef''s Github account and ran the `btrfsck --repair` twice on the

Hi! The problem is that the BTRFS raid10 filesystem without any understandable cause refuses to mount. Here is dmesg output: [77847.845540] device label linux-btrfs-raid10 devid 3 transid 45639 /dev/sdc1 [77848.633912] btrfs: allowing degraded mounts [77848.633917] btrfs: enabling auto defrag [77848.633919] btrfs: use lzo compression [77848.633922] btrfs: turning on flush-on-commit [77848.658879]

We forget to clear inode''s dirty_bytes and EXTENT_DIRTY at the end of write. Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com> --- fs/btrfs/file.c | 1 - fs/btrfs/inode.c | 5 ++++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c index e7872e4..3f3b4a8 100644 --- a/fs/btrfs/file.c +++ b/fs/btrfs/file.c @@ -1150,7 +1150,6 @@

Hello all We are experimenting with btrfs and we''ve run into some problems. We are running on two Sun Storage J4400 Arrays containing a total of 48 1 TB disks. With 24 disks in the btrfs: # mkfs.btrfs /dev/sd[b-y] WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using adding device /dev/sdc id 2 ... adding device /dev/sdy id 24 fs

3.8.0+ #3 This happened after ''umount /btrfs'' was interrupted by ctl-C # mount | egrep btrfs /dev/mapper/mpathe on /btrfs type btrfs (rw,degraded) # cat /etc/mtab | egrep btrfs /dev/mapper/mpathe /btrfs btrfs rw,degraded 0 0 # cat /proc/mounts | egrep btrfs # umount /btrfs umount: /btrfs: not mounted # -Anand -- To unsubscribe from this list: send the line "unsubscribe

Hello, On a newly created filesystem with btrfs-progs-git-20111009 and the 3.1.0-rc8 kernel I am getting the following error when doing btrfsck after main OS installation fs tree 256 refs 2 unresolved ref root 256 dir 256 index 2 namelen 8 name __active error 600 found 4215058432 bytes used err is 1 total csum bytes: 3962760 total tree bytes: 157192192 total fs tree bytes: 146976768

Hi all, I am using a single volume across two devices sdb7 and sda1, initially created on sdb7, and added sda1 using btrfs-vol later. The fstab entry: /dev/disk/by-id/scsi-SATA_ST31000333AS_9TE12DSC-part7 /mnt/btrfs btrfs defaults 1 2 Now after boot I get: ---- device fsid c4822885057410c-d2d65a83c2f15fb4 devid 1 transid 73034 /dev/sdb7 btrfs: failed to read chunk tree on sdb7 ---- So I have

From: Sergei Trofimovich <slyfox@gentoo.org> $ LDFLAGS=-static make gcc -lpthread -g -O0 -o btrfs btrfs.o btrfs_cmds.o scrub.o \ ctree.o disk-io.o radix-tree.o extent-tree.o print-tree.o root-tree.o dir-item.o file-item.o inode-item.o inode-map.o crc32c.o rbtree.o extent-cache.o extent_io.o volumes.o utils.o btrfs-list.o btrfslabel.o -static -luuid scrub.o: In function

I''m using Btrfs v0.20-rc1-253-g7854c8b on kernel 3.10.10-1-ARCH. I''ve been using this btrfs filesystem on an SSD for a little under a year with no problems until now. I noticed it was getting a bit full (~79%) and tried to do some cleanup by removing old snapshots. Immediately after, the filesystem went into read only mode. I then followed Hugo Mill''s advice (that was

To reproduce the bug: # mount -o nodatacow /dev/sda7 /mnt/ # dd if=/dev/zero of=/mnt/tmp bs=4K count=1 1+0 records in 1+0 records out 4096 bytes (4.1 kB) copied, 0.000136115 s, 30.1 MB/s # dd if=/dev/zero of=/mnt/tmp bs=4K count=1 conv=notrunc oflag=direct dd: writing `/mnt/tmp'': Input/output error 1+0 records in 0+0 records out btrfs_ordered_update_i_size() may return

This fixes: btrfs-list.c: Dans la fonction «ino_resolve» : btrfs-list.c:511: attention : déclaration implicite de la fonction « «strndup» » btrfs-list.c:511: attention : incompatible implicit declaration of built-in function «strndup» make: *** [btrfs-list.o] Erreur 1 and: btrfs.c: Dans la fonction «split_command» : btrfs.c:168: attention : déclaration implicite de la fonction « «strndup» »

Commit 5ac00add added a testnset mutex and code that disallows running administrative tasks in parallel. It is prevented that the device add/delete/balance/replace/resize operations are started in parallel. By mistake, the defragmentation operation was included in the check for mutually exclusiveness as well. This is fixed with this commit. Signed-off-by: Stefan Behrens