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: Thu, 24 Sep 2020 18:19:25 +0000 [thread overview]
Message-ID: <bug-202127-201763-VBabxAHYN6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202127-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202127
daimh@umich.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |PATCH_ALREADY_AVAILABLE
--- Comment #37 from daimh@umich.edu ---
Today another new machine had the same problem. I fixed it by upgrading the
firmware.
####Here is the info before the update
# /opt/MegaRAID/storcli/storcli /c0 show all |grep ^Firmware
Firmware Package Build = 24.19.0-0049
Firmware Version = 4.720.00-8220
# blockdev --getiomin --getioopt /dev/sdc
1048576
262144
# mkfs -t xfs /dev/sdc
meta-data=/dev/sdc isize=512 agcount=262, agsize=268434944
blks
= sectsz=4096 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=1
data = bsize=4096 blocks=70314098688, 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
SB stripe unit sanity check failed
Metadata corruption detected at 0x56324656db89, xfs_sb block 0x0/0x1000
libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1000
mkfs.xfs: Releasing dirty buffer to free list!
found dirty buffer (bulk) on free list!
SB stripe unit sanity check failed
Metadata corruption detected at 0x56324656db89, xfs_sb block 0x0/0x1000
libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1000
mkfs.xfs: writing AG headers failed, err=117
#####Then I upgraded with the command below and rebooted it
# /opt/MegaRAID/storcli/storcli /c0 download file=mr3316fw.rom
#####Here the info after the update
# /opt/MegaRAID/storcli/storcli /c0 show all |grep -i firmware
Firmware Package Build = 24.22.0-0071
Firmware Version = 4.740.00-8452
# blockdev --getiomin --getioopt /dev/sdc
262144
262144
#
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-09-24 18:19 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
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 [this message]
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-VBabxAHYN6@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).