From: Mark Tinguely <tinguely@sgi.com>
To: Rich Johnston <rjohnston@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfsprogs-3.1.11 pre-release please test!
Date: Wed, 01 May 2013 15:35:20 -0500 [thread overview]
Message-ID: <51817C88.4060208@sgi.com> (raw)
In-Reply-To: <51817712.6000807@sgi.com>
On 05/01/13 15:12, Rich Johnston wrote:
> Hi Folks,
>
> Here are the changes for this release:
>
> xfsprogs-3.1.11 (30 April 2013)
>
> - Support for relative paths in xfs_quota thanks to Satoru Takeuchi.
> - mkfs.xfs will always go into multidisk mode when filesystem
> geometry is specified on the command line.
> - Document all commands in xfs_io.
> - Remove setfl command from xfs_io.
> - xfs_metadump will obfuscate symlinks by path component.
> - mkfs.xfs no longer accepts geometry settings smaller than the
> physical sector size.
> - xfs_logprint now supports multiply-logged inode fields and
> handles continued inode transactions correctly.
> - kill XLOG_SET
> - Update release scripts to use git archive to address a
> missing source file reported by Arkadiusz Mi?kiewicz
> - Fix a build error with -Werror=format-security, reported
> by Arkadiusz Mi?kiewicz
> - mkfs.xfs no longer attempts to discard when -N option is used.
> - Update 'make deb' to use tarball
> - Sync up with log reservation changes in the kernel.
> - Fix possible unallocated memory access in fiemap.
> - Guard against string overflow in path_to_fspath.
> - Fix setup_cursor array allocation.
> - Fix free of unintialized pointer in xfs_acl_valid error path.
> - Guard against path string overflows.
> - Check strdup results properly in initallfs().
> - Fix attribute no_change_count logic.
> - Remove extraneous close() in fsrallfs().
> - xfs_repair now skips the freelist scan of a corrupt agf
> when in no-modify mode.
> - xfs_db now skips freelist scans of corrupt agfs.
> - Remove unconditional ASSERT(0) in xfs_repair.
> - Reduce bb_numrecs in bno/cnt btrees when log consumes all agf space.
> - Add depraction message for xfs_check.
> - xfs_quota allow user or group names beginning with digits reported by
> James Carter.
> - Fix manpages and usage() spelling, errors and omissions.
>
> I have placed a pre-release tarball here:
>
> ftp://oss.sgi.com/projects/xfs/cmd_tars/pre-release/xfsprogs-pre-3.1.11-3.tar.gz
>
>
> Please take a look and report any issues before next Wednesday (08 May
> 2013). If there are other patches which you feel are essential, now is
> the time to say so.
>
> Regards
> --Rich
The new lines (below) in xfs_check.sh breaks older xfstests:
xfs_check is deprecated and scheduled for removal in June 2014.
Please use xfs_repair -n <dev> instead.
xfstests' ./check thinks the TEST directory is inconsistent and stops.
I simply commented the lines out of the installed /usr/sbin/xfs_check
for my tests.
FSTYP -- xfs (debug)
PLATFORM -- Linux/x86_64 host 3.9.0-rc1+
MKFS_OPTIONS -- -f -bsize=4096 {SCRATCH_DEV}
MOUNT_OPTIONS -- {SCRATCH_DEV} {SCRATCH_MNT}
_check_xfs_filesystem: filesystem on {TEST_DEV} is inconsistent (c) (see
check.full)
Passed all 0 tests
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-01 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 20:12 xfsprogs-3.1.11 pre-release please test! Rich Johnston
2013-05-01 20:35 ` Mark Tinguely [this message]
2013-05-01 21:01 ` Eric Sandeen
2013-05-01 21:17 ` Mark Tinguely
2013-05-01 21:23 ` Eric Sandeen
2013-05-01 22:10 ` Dave Chinner
2013-05-02 13:34 ` Michael L. Semon
2013-05-02 14:45 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2013-04-30 20:01 Rich Johnston
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=51817C88.4060208@sgi.com \
--to=tinguely@sgi.com \
--cc=rjohnston@sgi.com \
--cc=xfs@oss.sgi.com \
/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