linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 202127] cannot mount or create xfs on a  597T device
Date: Tue, 22 Jan 2019 15:36:04 +0000	[thread overview]
Message-ID: <bug-202127-201763-FamnOFtBs7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202127-201763@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202127

--- Comment #26 from daimh@umich.edu ---
mount -o noalign or mount -o sunit=,swidth doesn't work. Here is the commands.

########old kernel
[root@watsons-s1 ~]# uname -a
Linux watsons-s1.mbni.org 4.17.14-arch1-1-ARCH #1 SMP PREEMPT Thu Aug 9
11:56:50 UTC 2018 x86_64 GNU/Linux
[root@watsons-s1 ~]# mkfs.xfs -V
mkfs.xfs version 4.17.0
[root@watsons-s1 ~]# mkfs.xfs -f /dev/sda
meta-data=/dev/sda               isize=512    agcount=557, agsize=268434944
blks
         =                       sectsz=4096  attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=0
data     =                       bsize=4096   blocks=149409103872, imaxpct=1
         =                       sunit=256    swidth=64 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=521728, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0


############new kernel
[root@watsons-s1 ~]# uname -a
Linux watsons-s1.mbni.org 4.20.3-arch1-1-ARCH #1 SMP PREEMPT Wed Jan 16
22:38:58 UTC 2019 x86_64 GNU/Linux
[root@watsons-s1 ~]# mkfs.xfs -V
mkfs.xfs version 4.19.0
[root@watsons-s1 ~]# mount -t xfs -o noalign /dev/sda
/treehouse/watsons_lab/s1/
mount: /treehouse/watsons_lab/s1: mount(2) system call failed: Structure needs
cleaning.
[root@watsons-s1 ~]# dmesg
[  289.750470] XFS (sda): SB stripe unit sanity check failed
[  289.750564] XFS (sda): Metadata corruption detected at
xfs_sb_read_verify+0x106/0x180 [xfs], xfs_sb block 0xffffffffffffffff
[  289.752487] XFS (sda): Unmount and run xfs_repair
[  289.753980] XFS (sda): First 128 bytes of corrupted metadata buffer:
[  289.755393] 00000000: 58 46 53 42 00 00 10 00 00 00 00 22 c9 7a 00 00 
XFSB.......".z..
[  289.756787] 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
................
[  289.758168] 00000020: 85 3d da cd 25 7c 48 e3 a7 56 b2 4c 8c d2 d5 35 
.=..%|H..V.L...5
[  289.759551] 00000030: 00 00 00 11 60 00 00 08 00 00 00 00 00 00 08 00 
....`...........
[  289.760939] 00000040: 00 00 00 00 00 00 08 01 00 00 00 00 00 00 08 02 
................
[  289.762308] 00000050: 00 00 00 01 0f ff fe 00 00 00 02 2d 00 00 00 00 
...........-....
[  289.763670] 00000060: 00 07 f6 00 bd a5 10 00 02 00 00 08 00 00 00 00 
................
[  289.765016] 00000070: 00 00 00 00 00 00 00 00 0c 0c 09 03 1c 00 00 01 
................
[  289.766432] XFS (sda): SB validate failed with error -117.
[root@watsons-s1 ~]# mount -t xfs -o sunit=256,swidth=64 /dev/sda
/treehouse/watsons_lab/s1/
mount: /treehouse/watsons_lab/s1: wrong fs type, bad option, bad superblock on
/dev/sda, missing codepage or helper program, or other error.
[root@watsons-s1 ~]# dmesg
[  316.159473] XFS (sda): stripe width (64) must be a multiple of the stripe
unit (256)

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

  parent reply	other threads:[~2019-01-22 15:36 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 19:54 [Bug 202127] New: cannot mount or create xfs on a 597T device bugzilla-daemon
2019-01-03 19:56 ` [Bug 202127] " bugzilla-daemon
2019-01-03 21:13 ` bugzilla-daemon
2019-01-03 22:18 ` bugzilla-daemon
2019-01-03 22:51   ` Dave Chinner
2019-01-03 22:51 ` bugzilla-daemon
2019-01-03 22:58 ` bugzilla-daemon
2019-01-03 23:22   ` Dave Chinner
2019-01-03 23:08 ` bugzilla-daemon
2019-01-03 23:12 ` bugzilla-daemon
2019-01-03 23:14 ` bugzilla-daemon
2019-01-03 23:17 ` bugzilla-daemon
2019-01-03 23:20 ` bugzilla-daemon
2019-01-03 23:22 ` bugzilla-daemon
2019-01-03 23:24 ` bugzilla-daemon
2019-01-03 23:32 ` bugzilla-daemon
2019-01-04  4:42 ` bugzilla-daemon
2019-01-04 21:59 ` bugzilla-daemon
2019-01-08 16:59   ` Emmanuel Florac
2019-01-04 22:02 ` bugzilla-daemon
2019-01-04 23:03   ` Dave Chinner
2019-01-04 23:03 ` bugzilla-daemon
2019-01-04 23:08 ` bugzilla-daemon
2019-01-05  1:36 ` bugzilla-daemon
2019-01-08 17:06 ` bugzilla-daemon
2019-01-08 17:59 ` bugzilla-daemon
2019-01-22 12:49 ` bugzilla-daemon
2019-01-22 21:52   ` Dave Chinner
2019-01-22 14:18 ` bugzilla-daemon
2019-01-22 14:35 ` bugzilla-daemon
2019-01-22 15:01 ` bugzilla-daemon
2019-01-22 15:36 ` bugzilla-daemon [this message]
2019-01-22 15:55 ` bugzilla-daemon
2019-01-22 17:38 ` bugzilla-daemon
2019-01-22 17:48 ` bugzilla-daemon
2019-01-22 17:48 ` bugzilla-daemon
2019-01-22 18:28 ` bugzilla-daemon
2019-01-22 21:52 ` bugzilla-daemon
2019-01-22 21:56 ` bugzilla-daemon
2019-01-22 22:59 ` bugzilla-daemon
2019-01-24 13:02 ` bugzilla-daemon
2019-03-25  8:46 ` bugzilla-daemon
2020-09-24 18:19 ` bugzilla-daemon
2020-09-24 18:52 ` bugzilla-daemon
2020-09-24 18:57 ` 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:
  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=bug-202127-201763-FamnOFtBs7@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-xfs@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).