search for: defragmenter

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

Dear all developers, I'm working with a lot of textual data in R and need to handle this batch by batch. The problem is that I read in batches of 10 000 documents and do some calculations that results in objects that consume quite some memory (calculate unigrams, 2-grams and 3-grams). In every iteration a new objects (~ 500 mB) is created (and I can't control the size, so a new object

Someone recently posted the following statement midway down the page at http://forums.gentoo.org/viewtopic-t-305871-postdays-0-postorder-asc-highlight-ext3+ordered+data-start-25.html >You don't need to defragment ext2/ext3 because as you use the >filesystem file blocks and inodes are moved around and reallocated >to keep the data nearly contiguous. It's not perfect, but it

I've read in many places that file systems on Linux do not suffer the same fragmentation problems of Windows systems. No one has provided a clear explanation as to why fragmentation is not an issue for file systems such as ext2/3, reiserfs, xfs, etc. Just curious.

When designing a filesystem, is fragmentation really an issue if access to the disk can be done using scatter-gather DMA techics ?

A) Resilver = Defrag. True/false? B) If I buy larger drives and resilver, does defrag happen? C) Does zfs send zfs receive mean it will defrag? -- This message posted from opensolaris.org

This fixes three issues on move extents ioctl without auto defrag: a) In ocfs2_find_victim_alloc_group(), we have to convert bits to block first in case of global bitmap. b) In ocfs2_probe_alloc_group(), when finding enough bits in block group bitmap, we have to back off move_len to start pos as well, otherwise it may corrupt filesystem. c) In ocfs2_ioctl_move_extents(), set me_threshold both for

This commit fixes three issues on non-auto defrag path (defragfs.ocfs2 doesn't set OCFS2_MOVE_EXT_FL_AUTO_DEFRAG on range.me_flags): - For ocfs2_find_victim_alloc_group(), old code forgot enlarge bitmap range for global_bitmap case. Old code could generate negative vict_bit. - For ocfs2_probe_alloc_group(), old code forgot back off move_len when finding enough bitmap space. Old code has

Before I'd try to defragment my whole filesystem (see attached mail for whole story) I figured "Let's try it on some file". So I did > xfs_bmap /raid/Temp/someDiskimage.iso [output shows 101 extents and 1 hole] Then I defragmented the file > xfs_fsr /raid/Temp/someDiskimage.iso extents before:101 after:3 DONE > xfs_bmap /raid/Temp/someDiskimage.iso [output shows 3

Hello everybody, reading about the speed improvements possible with (on boot) preloaded files (which should be continuous on disk) I searched for a ext3 defrag program. I found an ext2 defrag program (http://www.ibiblio.org/pub/Linux/system/filesystems/defrag-0.70.tar.gz, available in debian as defrag) which would have an optimal feature (moving files by a list) but refuses to work on ext3.

Hi, I ran into a strange behavior with libvirt snapshots. I have some vms running with thin-provisioned qcow2 disk images (libvirt 1.1.3 with fedora 20). * When I create a snapshot on the VM, the qcow file suddenly grows big, somewhat bigger than the maximum size of the disk. * When I delete the snapshot, the allocated disk space is not freed up, the qcow image remains the same size. However, if

Hello all, I understand that relatively high fragmentation is inherent to ZFS due to its COW and possible intermixing of metadata and data blocks (of which metadata path blocks are likely to expire and get freed relatively quickly). I believe it was sometimes implied on this list that such fragmentation for "static" data can be currently combatted only by zfs send-ing existing

Hi, I use btrfs on most of my volumes on my laptop, and I''ve always felt booting was very slow, but definitely sure is slow, is starting up Google Chrome: encrypted ext4: ~20s btrfs: ~2:11s I have tried different things to find out exactly what is the issue, but haven''t quite found it yet. Here''s some stuff I got from latencytop, not sure if would be helpful:

I've been trying to figure out why some large files are taking a long time to rsync (80GB file). With this file, the match process is taking days. I've added logging to verbose level 4. The output from match.c is at the point where it is writing out the "potential match at" message. In a 9 hour period the match verbiage has changed from: potential match at 14993337175 i=2976

Hi! Is there plans for fragmentation analyzing/reporting and online defragmentation tools for btrfs? And what about delayed allocation? Thanks!

Hi all, Here is my setup: Host1 ---> Router ----> Host2 When i run ttcp -t on Host1 while ttcp -r in Host2, the bandwidth that i can get is about 860 Kbytes/s, which is less than 7Mbps. But i am using NIC 10Mbps for all machines. Why is that so? Currently, i am experimenting with the example efcbq. I am using MGEN (a UDP traffic generator) to send 2 flows of traffic (EF and

https://bugzilla.netfilter.org/show_bug.cgi?id=1318 Bug ID: 1318 Summary: Fragmented packet filtering is broken iptables compatibility tools Product: nftables Version: unspecified Hardware: x86_64 OS: other Status: NEW Severity: normal Priority: P5 Component:

I have a huge problem with ZFS pool fragmentation. I started investigating problem about 2 weeks ago http://www.opensolaris.org/jive/thread.jspa?threadID=34423&tstart=0 I found workaround for now - changing recordsize - but I want better solution. The best solution would be a defragmentator tool, but I can see that it is not easy. When ZFS pool is fragmented then: 1. spa_sync function is

...etc does not mention it. Newer qemu can punch holes in files to make them sparse (where the kernel and filesystem also permit that), so that even though the physical size looks large, the actual usage of the file has shrunk after you delete an internal snapshot. But to date, no one has written a defragmenter for qcow2 images; the only way to reduce the physical size after it has once grown is to do something like 'qemu-img convert' to copy the image to a new file - but that action loses snapshots. > > Is there a way to free up the space allocated for snapshots? Punching holes should be...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 zpool and zfs report different free space because zfs takes into account an internal reservation of 32MB or 1/64 of the capacity of the pool, what is bigger. So in a 2TB Harddisk, the reservation would be 32 gigabytes. Seems a bit excessive to me... - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea at jcea.es -