From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 207367] Accraid / aptec / Microsemi / ext4 / larger then 16TB
Date: Mon, 20 Apr 2020 16:41:24 +0000 [thread overview]
Message-ID: <bug-207367-13602-B3JvUW8W7E@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207367-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207367
Christian Kujau (lists@nerdbynature.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lists@nerdbynature.de
--- Comment #1 from Christian Kujau (lists@nerdbynature.de) ---
Walter, please provide way more information here: describe the setup, provide
the exact error messages, did it work before, what changed that it doesn't work
anymore, etc. Maybe report the bug to the ext4 mailing list before logging a
tracking bug here. See also: [How to report Linux kernel
bugs](https://www.kernel.org/doc/html/latest/admin-guide/reporting-bugs.html#how-to-report-linux-kernel-bugs)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-04-20 16:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 8:44 [Bug 207367] New: Accraid / aptec / Microsemi / ext4 / larger then 16TB bugzilla-daemon
2020-04-20 16:41 ` bugzilla-daemon [this message]
2020-04-20 17:06 ` [Bug 207367] " bugzilla-daemon
2020-04-20 23:41 ` Christian Kujau
2020-04-21 3:55 ` [BISECTED] unable to mount devices larger than 16 TB (was: [Bug 207367] Accraid / aptec / Microsemi / ext4 / larger then 16TB) Christian Kujau
2020-04-20 23:51 ` [Bug 207367] Accraid / aptec / Microsemi / ext4 / larger then 16TB bugzilla-daemon
2020-04-21 4:20 ` Ritesh Harjani
2020-04-21 5:08 ` Dave Chinner
2020-04-21 6:48 ` Ritesh Harjani
2020-04-21 8:04 ` Christoph Hellwig
2020-04-21 16:29 ` Jan Kara
2020-04-21 16:45 ` Christoph Hellwig
2020-04-21 23:15 ` Theodore Y. Ts'o
2020-04-21 0:00 ` bugzilla-daemon
2020-04-21 4:20 ` bugzilla-daemon
2020-04-21 5:08 ` bugzilla-daemon
2020-04-21 6:48 ` bugzilla-daemon
2020-04-21 8:04 ` bugzilla-daemon
2020-04-21 9:03 ` bugzilla-daemon
2020-04-21 16:29 ` bugzilla-daemon
2020-04-21 16:45 ` bugzilla-daemon
2020-04-21 18:20 ` bugzilla-daemon
2020-04-21 23:15 ` 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-207367-13602-B3JvUW8W7E@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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).