From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:38622 "EHLO mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726175AbfAVW7C (ORCPT ); Tue, 22 Jan 2019 17:59:02 -0500 Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 1CCBD2B284 for ; Tue, 22 Jan 2019 22:59:02 +0000 (UTC) From: bugzilla-daemon@bugzilla.kernel.org Subject: [Bug 202127] cannot mount or create xfs on a 597T device Date: Tue, 22 Jan 2019 22:59:01 +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 #34 from Chris Murphy (bugzilla@colorremedies.com) --- (In reply to daimh from comment #22) > An update is that Broadcom engineer cannot reproduce the issue with Arch > Linux kernel 4.20.3-arch1-1-ARCH and mkfs.xfs version 4.19.0. The difference > is his raid-60 is 7T and 2T, while mine is 556T. That's unacceptable customer service. It's lazy, amateurish, and insulting. You've done their homework for them by tracking down this bug, they need to put more effort into providing an actual fix. I'd file a warranty claim regardless of whether it's currently under warranty or not, it's always been defective from the outset. I tried sending them a nastygram through corporate feedback, but that fails. Guess I'll send it by Twitter. -- You are receiving this mail because: You are watching the assignee of the bug.