Hi,
shortdesc: core code fixes, more static build targets, restore updates,
doc/help updates.
git://repo.or.cz/btrfs-progs-unstable/devel.git integration-20130318
shortlog:
Anand Jain (2):
btrfs-progs: update .gitignore file
btrfs-progs: print errno string when /dev/btrfs-control open fails
Antoine Sirinelli (1):
btrfs-progs: Add a rule to build a static mkfs.btrfs
David Marcin (1):
btrfs-progs: Fix error handling for failed reads in restore tool when
mirrors exist
Eric Sandeen (5):
btrfs-progs: close fd on return from label get/set functions
btrfs-progs: three new device/path helpers
btrfs-progs: don''t open-code mountpoint discovery in scrub cancel
btrfs-progs: rework get_fs_info to remove side effects
btrfs-progs: document force option in mkfs usage(); add long opt
Hugo Mills (1):
btrfs-progs: add Makefile rule for static build of btrfs-find-root
Josef Bacik (6):
Btrfs-progs: alloc our super copy in btrfs-find-root
Btrfs-progs: add an option for specifying the root to restore
Btrfs-progs: try other mirrors if decompression fails
Btrfs-progs: try other mirrors on read failure
btrfs-progs: add lzo compression support to restore
Btrfs-progs: give restore a list roots option
Matias Bjørling (1):
btrfs-progs: mkfs: add missing raid5/6 description
Peter Stuge (1):
restore: Split output directory and btrfs-local path search_dir()
parameters
short unsigned mail;
--
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/majordomo-info.html
Quoting David Sterba (2013-03-18 13:33:27)> Hi, > > shortdesc: core code fixes, more static build targets, restore updates, > doc/help updates. > > git://repo.or.cz/btrfs-progs-unstable/devel.git integration-20130318Thanks Dave, I''ve got this pulled in now and its on the master branch. -chris -- 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/majordomo-info.html
Hi,
finally removing the obsolete utilities, adding the fragmentation visualisation
tool in exchange, setting of io priority for scrub, few more fixes and updates
to the build system.
git://repo.or.cz/btrfs-progs-unstable/devel.git integration-20130320
david
---
shortlog:
Anand Jain (1):
btrfs-progs: defrag return zero on success
Arne Jansen (1):
Btrfs-progs: tool to visualize fragmentation
David Sterba (2):
btrfs-progs: convert: access name_len and file_type the old way
btrfs-progs: makefile: clean static targets
Goffredo Baroncelli (1):
Removing btrfsctl, btrfs-vol, btrfs-show
Josef Bacik (2):
Btrfs-progs: fix segfault when using tools fs with tree log
Btrfs-progs: fix memory leaks on cleanup
Sergei Trofimovich (1):
Makefile: allow user set LDFLAGS for libbtrfs.so as well
Stefan Behrens (1):
Btrfs-progs: make scrub IO priority configurable
--
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/majordomo-info.html
Am Mittwoch, 20. März 2013 schrieb David Sterba:> Hi, > > finally removing the obsolete utilities, adding the fragmentation > visualisation tool in exchange, setting of io priority for scrub, few > more fixes and updates to the build system.The fragmentation visuation tool works nicely. Tried it on about 200 GiB /home, almost no fragmentation, some 3-4%, but mostly 0.something%, and on about 20 GiB root, were some chunks were fragmented upto 30-40%. What kind of fragmentation does the tool count? From what I understand by looking at the source, extent fragmentation? 82 static void 83 print_bg(FILE *html, char *name, u64 start, u64 len, u64 used, u64 flags, 84 »······· u64 areas) 85 { 86 »·······double frag = (double)areas / (len / 4096) * 2; 87 88 »·······fprintf(html, "<p>%s chunk starts at %lld, size is %s, %.2f%% used, " 89 »·······»······· "%.2f%% fragmented</p>\n", chunk_type(flags), start, 90 »·······»······· pretty_sizes(len), 100.0 * used / len, 100.0 * frag); 91 »·······fprintf(html, "<img src=\"%s\" border=\"1\" />\n", name); 92 } Thanks, -- Martin ''Helios'' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- 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/majordomo-info.html
On Wed, Mar 20, 2013 at 09:08:49PM +0100, Martin Steigerwald wrote:> The fragmentation visuation tool works nicely. Tried it on about 200 GiB > /home, almost no fragmentation, some 3-4%, but mostly 0.something%, > and on about 20 GiB root, were some chunks were fragmented upto 30-40%. > > What kind of fragmentation does the tool count? From what I understand > by looking at the source, extent fragmentation?It''s a high-level view of the 1GB chunk fragmentation, reflecting the contiguous allocated vs free space. A partition with frequent rewrites is likely to contain more fragmented chunks as you observe for your / . david -- 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/majordomo-info.html