All of lore.kernel.org
 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: Fri, 04 Jan 2019 21:59:11 +0000	[thread overview]
Message-ID: <bug-202127-201763-29fOcgezjR@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 #15 from daimh@umich.edu ---
I have a few back and forth with Broadcom support. He checked some logs
generated by their standard error check script and the logs looks fine to him.

He asked to run mkfs.ext4 on the block device, it failed with an error message
"mkfs.ext4: Size of device (0x22c97a0000 blocks) /dev/sda too big to create a 
filesystem using a blocksize of 4096."

Then he asked me if I can create XFS and EXT4 on a smaller partition. I fdisked
the block device to two smaller partitions, one is 2T the other is 50T.
mkfs.ext4 worked on both partition, but mkfs.xfs still reports the same error.

Then I was told to contact you guys again. Here is his latest reply.

"I think it is a xfs issue here.  Can you go back to the developer ? What were
the changes from 4.17 to 4.19 ?

If the problem is caused by our firmware, ext4 would have failed."

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

  parent reply	other threads:[~2019-01-04 21:59 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 [this message]
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
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-29fOcgezjR@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.