similar to: Re: [Bug #27842] [regression?] hang with 2.6.37 on a BTRFS test machine

Hi! With 3.2-rc4 (probably earlier), Ext4 seems to remember what areas it trimmed: merkaba:~> fstrim -v /boot /boot: 224657408 bytes were trimmed merkaba:~> fstrim -v /boot /boot: 0 bytes were trimmed But BTRFS does not: merkaba:~> fstrim -v / /: 4431613952 bytes were trimmed merkaba:~> fstrim -v / /: 4341846016 bytes were trimmed Is it planned to add this feature to BTRFS

Hi! Today I converted my /home from Ext4 to BTRFS by reformatting and copying all over again. I created the filesystem with -l 16384 -n 16384 -d single -m single on an logical volume Intel SSD 320 and mount with compress=lzo,spacecache. Current state: merkaba:~> btrfs filesystem show failed to read /dev/sr0 Label: ''home'' uuid: […] Total devices 1 FS bytes used

Hi, I have btrfs volume, shared via samba. I have a directory of documents that I want to backup on my server. win7 reports a maximum of ~3.10MB/s transfer transferring the same directory on a ext4 samba share I get 25MB/s + Any ideas? Is it like that because of how btrfs works and is setup? Thanks, -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body

I would like to compute the MC test (rfm.test) available in the package MarkedPointProcess (for the data BITOEK for example) in order to test the dependence between the marks and their locations. Why the syntax of rfm.test is false here? I have the message : ****************************** ML WARNING! Forbidden values! -- if there are too many warnings try narrower lower and upper bounds for the

I came across the tidbit that ZFS has a contract guarantee that the data read back will either be correct (the checksum computed over the data read from the disk matches the checksum stored on disk), or you get an I/O error. Obviously, this greatly reduces the probability that the data is invalid. (Particularly when taken in combination with the disk firmware''s own ECC and checksumming.)

Martin Steigerwald reported a BUG_ON() where we were given a bogus bytenr to map. Turns out he is using > PAGESIZE leafsizes. The readahead stuff is called every time we do a completion, but we may not have finished reading in all the pages, so the bytenr we read off the node could be completely bogus. Fix this by only calling the readahead hook once all pages have been read in. Thanks,

Hi list, I have a few large image files (VMware workstation VMDKs and TrueCrypt containers) which I routinely back up over the network to a btrfs raid10 volume via bigsync (https://code.google.com/p/bigsync/). The VM images in particular get really fragmented due to CoW, which is expected. I haven''t yet switched off CoW on the backups directory mainly to experiment and see what

Hi, I have 4 machines, all converted to BTRFS about 6 months ago, now all running Ubuntu Quantal with kernel 3.5.0-17 The matter is that all these machines are now getting slower and slower everyday, every disk access causing the disk to be 100% busy for long periods, to the point that I''m now seriously considering migrating everything back to ext4... From the start BTRFS was "not

https://bugs.freedesktop.org/show_bug.cgi?id=34348 Summary: (regression/bisected) (2.6.37 nouveau/KMS) internal laptop display remains blank Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, this is a new attempt to improve the output of the command "btrfs fi df". The previous attempt received a good reception. However there was no a general consensus about the wording. Moreover I still didn''t understand how btrfs was using the disks. A my first attempt was to develop a new command which shows how the disks

Hello ext3 users and developers, I am gathering information for an article about journal filesystems with emphasis on write barrier functionality, how it works, why journalling filesystems need write barrier and the current implementation of write barrier support for different filesystems. Background of this is my own experience of three XFS crashes in one week:

Adding linux-btrfs to Cc. Am Freitag, 27. Januar 2012 schrieb Jeff Moyer: > Hi, Hi, > As it stands, generic_file_aio_write will call into generic_write_sync > when -EIOCBQUEUED is returned from __generic_file_aio_write. > EIOCBQUEUED indicates that an I/O was submitted but NOT completed. > Thus, we will flush the disk cache, potentially before the write(s) > even make it to

Hi! > [ANNOUNCE] Btrfs v0.9 > [...] > * Stripe size parameter to mkfs.btrfs (-s size_in_bytes). Extents will > be aligned to the stripe size for performance. > [...] http://fixunix.com/kernel/258991-[announce]-btrfs-v0-9-a.html versus > -s, --sectorsize size > Specify the sectorsize, the minimum block allocation. (man mkfs.btrfs with btrfs-tools

Hi! I scanned for relevant topics in the last two years but except for putting a swap file on compress=lzo this march I didn´t found anything. Does compression make sense on SSD? Or more specifically: 1) In what chunk sizes does BTRFS compress? How much data is affected when a byte is changed in a 2 GB file or so? Can compression cause more writes to the SSD in extreme circumstances? 2) It

It looks like it was a quiet cycle for vhost-net: probably because most of energy was spent on bugfixes that went in for 2.6.36. People are working on multiqueue, tracing but I'm not sure it'll get done in time for 2.6.37 - so here's a tree with a single patch that helps windows guests which we definitely want in the next kernel. Please merge for 2.6.37. Thanks! The following changes

It looks like it was a quiet cycle for vhost-net: probably because most of energy was spent on bugfixes that went in for 2.6.36. People are working on multiqueue, tracing but I'm not sure it'll get done in time for 2.6.37 - so here's a tree with a single patch that helps windows guests which we definitely want in the next kernel. Please merge for 2.6.37. Thanks! The following changes

Hi, I am new to btrfs, and just installed a new system with SLED 11 SP2 a few days ago. However the system seems to be in a real sad state now, saying there is no free space left on the device even though there is about 8GB left on the / filesystem. A defragment works sometimes but then it goes back to the original state a day or two later. Other times the command just won''t respond.

I just subscribed to this list so in case this subject has already been discussed at length, my apologies. I have been waiting for btrfs forever. I have been waiting for it to become reasonably stable. In the wake of escalating problems with my old hardware RAID setup, I decided now was the time to make the transition. At this point I have been completely transitioned to btrfs for nearly

For using SSDs: Are there any format/mount parameters that should be set for using btrfs on SSDs (other than the "ssd" mount option)? General questions: How long is the ''delay'' for the delayed alloc? Are file allocations aligned to 4kiB boundaries, or larger? What byte value is used to pad unused space? (Aside: For some, the erased state reads all 0x00, and for

Hello, I have created a btrfs filesystem with RAID1 setup having 2 disks. Everything works fine but when I try to umount the device and remount it in degraded mode, the data still goes into both the disk. ideally in degraded mode only one disk show disk activity and not the failed ones. System Config: Base OS: Slackware kernel: linux 3.3.2 "sar -pd 2 10" shows me that the data is