search for: defragg

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.

...mends disabling this latency to get around it, but in doing that you might as well just use the deadline scheduler. Some other interesting tidbits for those using NFS. NFS with many nfsd threads will create a lot of file system fragments when writing large files. XFS does have the advantage of a defragger (I hope some smart person will develop one for ext2/3/4), but I am still looking for a better way to protect against fragmentation then running a defragger, so if anyone has an alternative I'm all ears. Another hint for those using NFS with ESX, make sure your vmdk partitions are 4k aligned...

Hi. System is snv_56 sun4u sparc SUNW,Sun-Fire-V440, zil_disable=1 We see many operation on nfs clients to that server really slow (like 90 seconds for unlink()). It''s not a problem with network, there''s also plenty oc CPU available. Storage isn''t saturated either. First strange thing - normally on that server nfsd has about 1500-2500 number of threads. I did

...that previous thread, it was stated that it was impossible to have defrag work safely on an ext3 partition. I do not see why this is so. If ext2 could be given a journal to make it crash resistant, then why can't defrag be given the same thing? Another comment was made saying that such a defragger could not possibly be done only in userspace. Unless you're talking about online defragmentation, then manipulating the filesystem offline to repack it is entirely possible from userspace. Is there still no way to do what I am trying? P.S. Please CC me on replies, as I am not subscribed...

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

The default blocksize is 128K. If you are using mirrors, then each block on disk will be 128K whenever possible. But if you''re using raidzN with a capacity of M disks (M disks useful capacity + N disks redundancy) then the block size on each individual disk will be 128K / M. Right? This is one of the reasons the raidzN resilver code is inefficient. Since you end up waiting for the

...++++++++++++++++++++-- 2 files changed, 26 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c index 20196f4..59b566d 100644 --- a/fs/btrfs/disk-io.c +++ b/fs/btrfs/disk-io.c @@ -3056,6 +3056,9 @@ int close_ctree(struct btrfs_root *root) /* clear out the rbtree of defraggable inodes */ btrfs_run_defrag_inodes(fs_info); + /* sync all the dirty pages which are made by auto defrag */ + sync_filesystem(fs_info->sb); + /* * Here come 2 situations when btrfs is broken to flip readonly: * diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c index 2b3...

-----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 -

Hello, This patch series adds an initial implementation of restriper (it''s a clever name for relocation framework that allows to do selective profile changing and selective balancing with some goodies like pausing/resuming and reporting progress to the user. Profile changing is global (per-FS) so far, per-subvolume profiles require some discussion and can be implemented in future.

Hi all - Here''s my current error handling patchset, against 3.1-rc8. Almost all of this patchset is preparing for actual error handling. Before we start in on that work, I''m trying to reduce the surface we need to worry about. It turns out that there is a ton of code that returns an error code but never actually reports an error. The patchset has grown to 65 patches. 46 of them