linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: clm@fb.com
Subject: Btrfs progs release 4.9.1
Date: Fri, 27 Jan 2017 15:25:45 +0100	[thread overview]
Message-ID: <20170127142545.19038-1-dsterba@suse.com> (raw)

Hi,

btrfs-progs version 4.9.1 have been released.

Changes:
* check:
  * use correct inode number for lost+found files
  * lowmem mode: fix false alert on dropped leaf
* size reports: negative numbers might appear in size reports during device
  deletes (previously in EiB units)
* mkfs: print device being trimmed
* defrag: v1 ioctl support dropped
* quota: print message before starting to wait for rescan
* qgroup show: new option to sync before printing the stats
* other:
  * corrupt-block enhancements
  * backtrace and co. cleanups
  * doc fixes

Changes since rc1:
* change name of one test directory, duplicate numbers

Tarballs: https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git

Shortlog:

David Sterba (18):
      btrfs-progs: make negative number pretty printing optional
      btrfs-progs: enable negative numbers for unallocated device space
      btrfs-progs: mkfs: print device name while trimming
      btrfs-progs: defrag: force using v2 defrag ioctl and make default 32M threshold actually work
      btrfs-progs: defrag: remove v1 ioctl support
      btrfs-progs: qgroups show: clean up errno passing
      btrfs-progs: qgroup show: refine error messages
      btrfs-progs: tests: 005-qgroup-show
      btrfs-progs: kerncompat: add separate trace print for BUG_ON
      btrfs-progs: kerncompat: pass exact condition value from ASSERT
      btrfs-progs: kerncompat: disconnect assert and warning messages
      btrfs-progs: kerncompat: simplify warning_trace
      btrfs-progs: qgroup show: do not error if sync fails
      btrfs-progs: tests: add variable quotation to cli-tests
      btrfs-progs: tests: use built binaries for 004-send-parent-multi-subvol
      btrfs-progs: mkfs/convert: separate the convert part from make_btrfs
      btrfs-progs: update CHANGES for v4.9.1
      Btrfs progs v4.9.1

Esteve Fernandez (1):
      btrfs-progs: docs: fix typo in btrfs-subvolume

Goldwyn Rodrigues (2):
      btrfs-progs: check: get the highest inode for lost+found
      btrfs-progs: sanitize - Use correct source for memcpy

Jeff Mahoney (1):
      btrfs-progs: quota: fix printing during wait mode

Lakshmipathi.G (2):
      btrfs-progs: corrupt-block: Include inode nlink field
      btrfs-progs: corrupt-block: Include more inode fields

Nicholas D Steeves (1):
      btrfs-progs: Fix spelling/typos in user-facing strings

Qu Wenruo (2):
      btrfs-progs: check: fix false alert on dropped leaf in lowmem mode
      btrfs-progs: Fix disable backtrace assert error

Tsutomu Itoh (3):
      btrfs-progs: qgroup: add sync option to 'qgroup show'
      btrfs-progs: qgroup: change the value of sort option
      btrfs-progs: tests: add test for --sync option of qgroup show

Zygo Blaxell (1):
      btrfs-progs: utils: negative numbers are more plausible than sizes over 8 EiB


                 reply	other threads:[~2017-01-27 14:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170127142545.19038-1-dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).