linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Btrfs progs pre-release 4.14-rc1
@ 2017-11-14 15:33 David Sterba
  2017-11-17 16:48 ` Uli Heller
  0 siblings, 1 reply; 4+ messages in thread
From: David Sterba @ 2017-11-14 15:33 UTC (permalink / raw)
  To: linux-btrfs; +Cc: clm

Hi,

a pre-release has been tagged.

Changes:
  * build: libzstd now required by default
  * check: more lowmem mode repair enhancements
  * subvol set-default: also accept path
  * prop set: compression accepts no/none, same as ""
  * filesystem usage: enable for filesystem on top of a seed device
  * rescue: new command fix-device-size
  * other
    * new tests
    * cleanups and refactoring
    * doc updates

ETA for 4.14 is in +2 days (2017-11-16).

Mailinglist patch backlog has grown again, I'll have to do more minor releases
to get the features and fixes merged. No concrete plans for now, some patchsets
are almost ready so they'll probably go first.

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:

Baruch Siach (1):
      btrfs-progs: convert: add missing types header

Benjamin Peterson (1):
      btrfs-progs: docs: correct grammar

David Sterba (24):
      btrfs-progs: help: print multiple syntax schemas on separate lines
      btrfs-progs: prop: also allow "none" to disable compression
      btrfs-progs: docs: update btrfs-properties
      btrfs-progs: image: move metadump definitions to own header
      btrfs-progs: build: use variables for btrfs-image images
      btrfs-progs: image: start a new header for sanitization functions
      btrfs-progs: image: introduce symbolic names for the sanitization modes
      btrfs-progs: image: pass rb_root to find_collisions
      btrfs-progs: image: drop unused parameter from sanitize_xattr
      btrfs-progs: image: pass sanitize mode and name tree separately to sanitize_inode_ref
      btrfs-progs: image: pass sanitize mode and name tree separately to sanitize_dir_item
      btrfs-progs: image: pass sanitize mode and name tree separately to sanitize_name
      btrfs-progs: image: move sanitization to new file
      btrfs-progs: don't use __u8 for fsid buffers
      btrfs-progs: tests: don't pass size to prepare_test_dev if not necessary
      btrfs-progs: tests: extend fsck/028 to test fix-device-size and mount
      btrfs-progs: docs: update mount options
      btrfs-progs: docs: add impact of atime/noatime
      btrfs-progs: docs: add note about mount option applicability
      btrfs-progs: build: require libzstd support by default
      btrfs-progs: build: mention library dependency for reiserfs
      btrfs-progs: docs: move the rescue fix-device-size command and update
      btrfs-progs: update CHANGES for v4.14
      Btrfs progs v4.14-rc1

Lakshmipathi.G (1):
      btrfs-progs: tests/common: Display warning only after searching for btrfs kernel module

Liu Bo (1):
      btrfs-progs: do not add stale device into fs_devices

Lu Fengqi (7):
      btrfs-progs: qgroup: fix qgroup show sort by multi items
      btrfs-progs: test: Add test image for lowmem mode file extent interrupt
      btrfs-progs: lowmem check: Output more detailed information about file extent interrupt
      btrfs-progs: lowmem check: Fix false alert about referencer count mismatch
      btrfs-progs: test: Add test image for lowmem mode referencer count mismatch false alert
      btrfs-progs: qgroup: cleanup the redundant function add_qgroup
      btrfs-progs: qgroup: split update_qgroup to reduce arguments

Misono, Tomohiro (6):
      btrfs-progs: subvol: change set-default to also accept path
      btrfs-progs: test: add new cli-test for subvol get/set-default
      btrfs-progs: fi: move dev_to_fsid to cmds-fi-usage for later use
      btrfs-progs: fi: enable fi usage for filesystem on top of seed device
      btrfs-progs: device: add description of alias to help message
      btrfs-progs: doc: add description of missing and example, of device remove

Pavel Kretov (1):
      btrfs-progs: defrag: add a brief warning about ref-link breakage

Qu Wenruo (14):
      btrfs-progs: tests: Allow check test to repair in lowmem mode for certain errors
      btrfs-progs: mkfs: avoid BUG_ON for chunk allocation when ENOSPC happens
      btrfs-progs: mkfs: avoid positive return value from cleanup_temp_chunks
      btrfs-progs: mkfs: fix overwritten return value for mkfs
      btrfs-progs: mkfs: error out gracefully for --rootdir
      btrfs-progs: convert: Open the fs readonly for rollback
      btrfs-progs: mkfs: refactor test_minimum_size to use the calculated minimal size
      btrfs-progs: rescue: Fix zero-log mounted branch
      btrfs-progs: Introduce function to fix unaligned device size
      btrfs-progs: Introduce function to fix super block total bytes
      btrfs-progs: rescue: Introduce fix-device-size
      btrfs-progs: check: Also check and repair unaligned/mismatch device and super sizes
      btrfs-progs: tests/fsck: Add test case image for 'rescue fix-dev-size'
      btrfs-progs: print-tree: Print offset as tree objectid for ROOT_ITEM

Satoru Takeuchi (1):
      btrfs-progs: allow "no" to disable compression for convenience

Su Yue (28):
      btrfs-progs: check: enable repair in lowmem mode
      btrfs-progs: check: repair inode nbytes in lowmem mode
      btrfs-progs: check: repair dir inode isize in lowmem mode
      btrfs-progs: check: repair inode orphan item in lowmem mode
      btrfs-progs: check: change find_inode_ref()'s arg
      btrfs-progs: check: modify check_fs_first_inode()
      btrfs-progs: check: change find_dir_index/item
      btrfs-progs: check: introduce print_inode_ref()
      btrfs-progs: check: introduce print_dir_item_err()
      btrfs-progs: check: adjustments for further repair
      btrfs-progs: check: introduce repair_inode_item_missing()
      btrfs-progs: check: introduce repair_fs_first_inode()
      btrfs-progs: check: repair dir_item and inode_ref in lowmem mode
      btrfs-progs: check: count dir inode isize again
      btrfs-progs: check: repair inode nlink in lowmem
      btrfs-progs: check: punch_extent_hole in lowmem
      btrfs-progs: check: special case for last item
      btrfs-progs: check: change the way lowmem mode traverses metadata
      btrfs-progs: check: delete wrong items in lowmem repair
      btrfs-progs: check: introduce repair_chunk_item()
      btrfs-progs: check: introduce repair_tree_block_ref()
      btrfs-progs: check: introduce repair_extent_data_item()
      btrfs-progs: check: repair block group accounting in lowmem mode
      btrfs-progs: check: return value of check_extent_refs
      btrfs-progs: check: call repair_root_items before any repairs
      btrfs-progs: check: error or return value of repair_root_items()
      btrfs-progs: check: check extent_inline_ref in lowmem
      btrfs-progs: fsck-tests: 027/bad_extent_inline_ref_type


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Btrfs progs pre-release 4.14-rc1
  2017-11-14 15:33 Btrfs progs pre-release 4.14-rc1 David Sterba
@ 2017-11-17 16:48 ` Uli Heller
  2017-11-17 20:08   ` Nick Terrell
  0 siblings, 1 reply; 4+ messages in thread
From: Uli Heller @ 2017-11-17 16:48 UTC (permalink / raw)
  To: linux-btrfs

I tried to compile these on ubuntu-14.04 running 4.4.0-98-generic
- I had to install libzstd-dev
- I had to disable the zstd tests

Do you think this ends up in a working binary? Or am I doing something 
strange?

Best regards, Uli

-- 
Uli Heller


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Btrfs progs pre-release 4.14-rc1
  2017-11-17 16:48 ` Uli Heller
@ 2017-11-17 20:08   ` Nick Terrell
  2017-11-18  9:03     ` Uli Heller
  0 siblings, 1 reply; 4+ messages in thread
From: Nick Terrell @ 2017-11-17 20:08 UTC (permalink / raw)
  To: Uli Heller; +Cc: linux-btrfs@vger.kernel.org


> On Nov 17, 2017, at 8:48 AM, Uli Heller <uli.heller@daemons-point.com> wrote:
> 
> I tried to compile these on ubuntu-14.04 running 4.4.0-98-generic
> - I had to install libzstd-dev
> - I had to disable the zstd tests
> 
> Do you think this ends up in a working binary? Or am I doing something strange?

You'll need to install libzstd-dev to compile with zstd enabled, since you
need the libraries and headers. What version of libzstd do you have? You'll
need a version >= 0.8.1 in order to read the compressed data.

On the zstd side, we're working on getting the version of zstd in Ubuntu
16.04 upgraded from 0.5.1 to a version >= 1.0.0 [1]. zstd-0.5.1 was
released before the format stabilized, and can't read data produced by zstd
>= 0.6.

I would expect the zstd tests to fail if the zstd version is < 0.8.1.
Otherwise, could you tell me which version of zstd you have, and I'll
attempt to reproduce the issue.

[1] https://bugs.launchpad.net/xenial-backports/+bug/1717040

-Nick

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Btrfs progs pre-release 4.14-rc1
  2017-11-17 20:08   ` Nick Terrell
@ 2017-11-18  9:03     ` Uli Heller
  0 siblings, 0 replies; 4+ messages in thread
From: Uli Heller @ 2017-11-18  9:03 UTC (permalink / raw)
  To: Nick Terrell; +Cc: linux-btrfs@vger.kernel.org

Am 17.11.2017 um 21:08 schrieb Nick Terrell:
>> On Nov 17, 2017, at 8:48 AM, Uli Heller <uli.heller@daemons-point.com> wrote:
>>
>> I tried to compile these on ubuntu-14.04 running 4.4.0-98-generic
>> - I had to install libzstd-dev
>> - I had to disable the zstd tests
>>
>> Do you think this ends up in a working binary? Or am I doing something strange?
> You'll need to install libzstd-dev to compile with zstd enabled, since you
> need the libraries and headers. What version of libzstd do you have? You'll
> need a version >= 0.8.1 in order to read the compressed data.

I compiled and installed version 1.3.2. I didn't verify if this version 
is actually working OK.
The tests run during the build for quite some time and I didn't observe 
an error, so I assumed
it ought to be fine.

> On the zstd side, we're working on getting the version of zstd in Ubuntu
> 16.04 upgraded from 0.5.1 to a version >= 1.0.0 [1]. zstd-0.5.1 was
> released before the format stabilized, and can't read data produced by zstd
>> = 0.6.
> I would expect the zstd tests to fail if the zstd version is < 0.8.1.
> Otherwise, could you tell me which version of zstd you have, and I'll
> attempt to reproduce the issue.

OK, so the success of the zstd tests depend on the version of the 
library, not the version
of the kernel, right?

I can offer to send some output of the failing tests if it helps.

Thanks a lot + best regards, Uli

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-11-18  9:03 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-11-14 15:33 Btrfs progs pre-release 4.14-rc1 David Sterba
2017-11-17 16:48 ` Uli Heller
2017-11-17 20:08   ` Nick Terrell
2017-11-18  9:03     ` Uli Heller

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