From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:53846 "EHLO mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726105AbfADV7M (ORCPT ); Fri, 4 Jan 2019 16:59:12 -0500 Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 9C88028435 for ; Fri, 4 Jan 2019 21:59:11 +0000 (UTC) From: bugzilla-daemon@bugzilla.kernel.org Subject: [Bug 202127] cannot mount or create xfs on a 597T device Date: Fri, 04 Jan 2019 21:59:11 +0000 Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: linux-xfs@vger.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.