archive mirror
 help / color / mirror / Atom feed
Subject: [Bug 215687] New: chown behavior on XFS is changed
Date: Tue, 15 Mar 2022 08:12:27 +0000	[thread overview]
Message-ID: <> (raw)

            Bug ID: 215687
           Summary: chown behavior on XFS is changed
           Product: File System
           Version: 2.5
    Kernel Version: xfs-5.18-merge-1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: XFS
        Regression: No

From our regular regression test on XFS, we found a failure which never failed
# prove -rf /root/git/pjd-fstest/tests/chown/00.t 
/root/git/pjd-fstest/tests/chown/00.t .. 83/171 
not ok 84
not ok 88
/root/git/pjd-fstest/tests/chown/00.t .. Failed 2/171 subtests 

Test Summary Report
/root/git/pjd-fstest/tests/chown/00.t (Wstat: 0 Tests: 171 Failed: 2)
  Failed tests:  84, 88
Files=1, Tests=171, 31 wallclock secs ( 0.10 usr  0.04 sys +  1.04 cusr 15.50
csys = 16.68 CPU)
Result: FAIL

That means chown behavior has been changed on XFS. To reproduce this failure
you can:
1) mkfs.xfs -f /dev/sdb1
2) mount /dev/sdb1 /mnt/test
3) cd /mnt/test
4) git clone git://
5) cd pjd-fstest; make;
6) echo -e "os=Linux\nfs=xfs" > tests/conf
7) cd /mnt/test
8) prove -rf /path/to/pjd-fstest/tests/chown/00.t

I'm going to look into it, to found out what specified behavior is changed.

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-03-15  8:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15  8:12 bugzilla-daemon [this message]
2022-03-15  8:30 ` [Bug 215687] chown behavior on XFS is changed bugzilla-daemon
2022-03-15  9:21 ` bugzilla-daemon
2022-03-24 10:22 ` [Bug 215687] New: " Thorsten Leemhuis
2022-03-24 12:50   ` Thorsten Leemhuis
2022-03-24 10:22 ` [Bug 215687] " bugzilla-daemon
2022-03-24 12:00 ` bugzilla-daemon
2022-03-24 12:50 ` bugzilla-daemon

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:

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

  git send-email \ \ \ \

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