search for: nodatasum

Hello, some time ago we discussed on #btrfs that the nocow attribute for files wasn''t working (around 3.3 or 3.4 kernels). That was evident by files fragmenting even with the attribute set. Chris mentioned to find a fix quickly for that, and posted some lines of change into irc. But recently someone mentioned that 3.6-rc looks like still not respecting nocow for files. Is there really

Hello, I''m using kernel 3.1.0 and I have both / and /home as btrfs. I used suspend to ram quite often and never had a problem, but yesterday I''ve suspended to get into a plane and when I resumed my /home was all about input/output errors. Reboot did not help either. My root (/) did not suffer any problems. Today I''ve upgraded btrfs-progs to latest GIT and tried scrub

...olume quotas and inherited space usage information * Snapshot removal * QA Suite for automated regression testing * Reserved space for online fsck and the ability to add storage so that a * background extent allocation check can proceed * Additional ioctls to set per-inode attributes (nodatacow, nodatasum, etc) So I think all of those are still true. Things that I know are being worked on are * async block group cacheing - me * locking changes - Chris * backref stuff - Yan Som other things off the top of my head are * a better way to cache block groups in general, for this I was thinking of a...

...when the filesystem is mounted with nodatacow. I''m using this as a workaround since subvolumes can''t be mounted with different options simultaneously. ie. one with COW, one with nodatacow Any ideas why the flags are being ignored? I''m running 32bit 3.3rc4 with noatime,nodatasum,space_cache,autodefrag,inode_cache on a 3 disk RAID0 data RAID1 metadata filesystem. Thanks, Kyle -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/maj...

...t into the same patch set. The first feature adds printk statements in case scrub finds an error which list all affected files. You will need patch 1, 2 and 3 for that. The second feature adds the trigger which enables us to correct i/o errors in case the affected extent does not have a checksum (nodatasum), eventually. You will need patch 1, 4, 5 and 6 for that. I tried to apply all patches to the current cmason/for-linus branch and to Arne''s current for-chris branch. They do apply with no errors (some offsets possible). The new ioctl()s can be tested from usermode by applying the patch s...

Hi, I've recently benchmarked btrfs v0.11 & v0.12 against ext2, ext3, ext4, jfs, reiserfs and xfs. OS: Ubuntu Hardy Kernel: 2.6.24(-5-server) Hardware: --------- Fu-Si Primergy RX330 S1 * AMD Opteron 2210 1.8 GHz * 1 GB RAM * 3 x 73 GB, 3Gb/s, hot plug, 10k rpm, 3.5" SAS HDD * LSI RAID 128 MB Fu-Si Econel 200 * Intel Xeon 5110 * 512 MB RAM

The kernel patch series just sent (Subject: "Btrfs: scrub: print path to corrupted files and trigger nodatasum fixup") introduces two new ioctls to do in-kernel filesystem path construction. This series provides the corresponding userspace changes, adding two new commands to the btrfs utility: -- btrfs resolve inode [-v] <inode> <path> resolves an <inode> to all filesystem paths loc...

...detect changes, that the data read is the same as was once written, that would be a major selling point for btrfs for me personally. The closest I was able to find was that btrfs uses crc32c currently for data and metadata checksumming and that this can be turned off if so desired (using the "nodatasum" mount option), but nothing about what the file system code does or is supposed to do in the face of a checksum mismatch. -- Michael Kjörling • http://michael.kjorling.se • michael@kjorling.se “People who think they know everything really annoy those of us who...

...lesize=10737418240 --bsrange=512b-64k --scramble_buffers=1 --nrfiles=1 --overwrite=1 --ioengine=sync --filename=file-1 --name=job0 --name=job1 --name=job2 --name=job3 --name=job4 --name=job5 --name=job6 --name=job7 The files are preallocated with fallocate before the fio run. Mount options: noatime,nodatasum,nodatacow,nospace_cache Can somebody please advise on how to address this issue, and, if possible, how to solve it on kernel 3.6. Thanks, Alex. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo...

Hi there, Just gave 0.13 a spin against XFS (both with default mkfs options) on my SATA tower and was impressed by how much performance has improved since last time I played with it (v0.5)! It pretty much matched XFS for I/O performance and had much better file creation/deletion performance. http://www.csamuel.org/2008/03/23/btrfs-013-and-xfs-benchmarks cheers, Chris -- Chris Samuel :

...per.c +++ b/fs/btrfs/super.c @@ -327,7 +327,7 @@ enum { static match_table_t tokens = { {Opt_degraded, "degraded"}, {Opt_subvol, "subvol=%s"}, - {Opt_subvolid, "subvolid=%d"}, + {Opt_subvolid, "subvolid=%s"}, {Opt_device, "device=%s"}, {Opt_nodatasum, "nodatasum"}, {Opt_nodatacow, "nodatacow"}, @@ -673,8 +673,8 @@ static int btrfs_parse_early_options(const char *options, fmode_t flags, { substring_t args[MAX_OPT_ARGS]; char *device_name, *opts, *orig, *p; + char *num = NULL; int error = 0; - int intarg; if (!opt...

...================================================================ --- btrfs-unstable.orig/super.c 2008-06-10 10:40:18.000000000 +0200 +++ btrfs-unstable/super.c 2008-06-10 10:47:47.000000000 +0200 @@ -65,7 +65,7 @@ static void btrfs_put_super (struct supe } enum { - Opt_degraded, Opt_subvol, Opt_nodatasum, Opt_nodatacow, + Opt_degraded, Opt_subvol, Opt_device, Opt_nodatasum, Opt_nodatacow, Opt_max_extent, Opt_max_inline, Opt_alloc_start, Opt_nobarrier, Opt_ssd, Opt_err, }; @@ -73,6 +73,7 @@ enum { static match_table_t tokens = { {Opt_degraded, "degraded"}, {Opt_subvol, "subv...

...n''t know if it''s the final design and while the first and last points are minor inconveniences the second one is quite major. At this time it doesn''t prevent silent corruption from going unnoticed. I think that reading from such blocks should return EIO (unless mounted nodatasum) or at least a broadcast message noting that a corrupted block is being returned to userspace. I''ve also been thinking about tiered storage (meaning 2+, not only two-tiered) and have some ideas about it. I think that there need to be 3 different mechanisms working together to achiev...

...ong in my opinion. I would like to get some advice on how to improve these times and/or some analysis from a developer. I tried balance after the test and deleted the last remaining file 21.tst, but it would take it 1.5 MINUTES to run! My conclusion is that it is broken. I also tried nodatacow and nodatasum and got no obvious improvements. Defrag would return immediately and I could run it during the test too without impacting the test numbers. Thanks, Nik Markovic -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org...

...hannel), took us ~ 30min to complete using XFS (mounted with "nobarrier", data security is not an issue in this scenario). When using btrfs on the same hardware (same SSD, same system), it took us ~ 120min. The filesystem was mounted using the following options: > mount -t btrfs -o nodatasum,nodatacow,nobarrier,ssd,noacl,notreelog,noatime,nodiratime /dev/sdg /data-ssd3 (Both measurements done under linux-2.6.34). Looks like btrfs is not really tuned to perform well in the above scenario. I would appreciate any advise on how to improve btrfs'' performance for the above scena...

...out-of-memory killer trying to kill some tasks or there are > page-allocation failures that btrfs or other kernel module > experiences. > > This issue is consistently reproducible & to do that this is what I do: > # mkfs.btrfs on a blockdevice > # mount with "rw,noatime,nodatasum,nodatacow,nospace_cache" options > # btrfs quota enable /mntpoint > # btrfs qgroup create 100 /mntpoint > # I setup a subvolume under the mountpoint & fallocate a file of fixed size. > # Perform 4K write random IO with 4 worker threads with the > application opening with O_...

This series adds an initial implementation for scrub. It works quite straightforward. The usermode issues an ioctl for each device in the fs. For each device, it enumerates the allocated device chunks. For each chunk, the contained extents are enumerated and the data checksums fetched. The extents are read sequentially and the checksums verified. If an error occurs (checksum or EIO), a good copy

I have a 3 disk raid1 filesystem mounted with nodatacow. I have a folder in said filesystem with the ''C'' NOCOW & ''Z'' Not_Compressed flags set for good measure. I then copy in a large file and proceed to make random modifications. Filefrag shows no additional extents created, good so far. A big thank you to the those devs who got that working. However, after

Currently compression and I assume if encryption is implemented it is turned on or off during mount. There are however many times when a user may want to select which files/directories they want to compress or encrypt. This will also be helpful when implementing btrfs support in grub for example. We can say the disk can be compressed/encrypted except for /boot so compression/encryption

I''ve been working to try to improve the write-ahead log''s performance, and I found that the bottleneck addresses in the checksum items, especially when we want to make a random write on a large file, e.g a 4G file. Then a idea for this suggested by Chris is to use sub transaction ids and just to log the part of inode that had changed since either the last log commit or the last