linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 89511] USB-storage mount error
Date: Sat, 03 Jan 2015 23:47:44 +0000	[thread overview]
Message-ID: <bug-89511-13602-K6rhD6m5QA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-89511-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=89511

--- Comment #34 from Jun Itou <itou_jun@infoseek.jp> ---
When it is ext2, this phenomenon does not occur.
Is a journal function a problem?
Therefore will it be a thing called "write through"?

And I think of compatibility of ext4 to be contents by a version of kernel.
That when I format it in 3.2.62 and do mount in 3.2.63, an error appears in
"write through".

I looked at the source, but only a difference is checked because I do not
understand specifications.
Detailed one, please support it.

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

  parent reply	other threads:[~2015-01-03 23:47 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10  2:35 [Bug 89511] New: USB-storage mount error bugzilla-daemon
2014-12-10 17:17 ` [Bug 89511] " bugzilla-daemon
2014-12-10 22:33 ` bugzilla-daemon
2014-12-10 22:51 ` bugzilla-daemon
2014-12-11 10:00 ` bugzilla-daemon
2014-12-11 19:31 ` bugzilla-daemon
2014-12-12 13:01 ` bugzilla-daemon
2014-12-13  7:41 ` bugzilla-daemon
2014-12-16 21:50 ` bugzilla-daemon
2014-12-19  8:36 ` bugzilla-daemon
2014-12-19  8:41 ` bugzilla-daemon
2014-12-19  8:42 ` bugzilla-daemon
2014-12-19  8:44 ` bugzilla-daemon
2014-12-19  8:44 ` bugzilla-daemon
2014-12-19  8:48 ` bugzilla-daemon
2014-12-19  8:50 ` bugzilla-daemon
2014-12-19 18:51 ` bugzilla-daemon
2014-12-19 21:15 ` bugzilla-daemon
2014-12-19 21:16 ` bugzilla-daemon
2014-12-19 21:19 ` bugzilla-daemon
2014-12-19 22:11 ` bugzilla-daemon
2014-12-20  1:48 ` bugzilla-daemon
2014-12-20  1:50 ` bugzilla-daemon
2014-12-20  1:50 ` bugzilla-daemon
2014-12-20  1:55 ` bugzilla-daemon
2014-12-25  7:45 ` bugzilla-daemon
2014-12-25 21:03 ` bugzilla-daemon
2014-12-26  7:56 ` bugzilla-daemon
2014-12-26 15:51 ` bugzilla-daemon
2014-12-26 22:08 ` bugzilla-daemon
2014-12-27 12:51 ` bugzilla-daemon
2014-12-27 13:01 ` bugzilla-daemon
2014-12-28  8:15 ` bugzilla-daemon
2014-12-28  8:24 ` bugzilla-daemon
2014-12-28  8:32 ` bugzilla-daemon
2015-01-02  0:49 ` bugzilla-daemon
2015-01-03 23:47 ` bugzilla-daemon [this message]
2015-01-04 20:12 ` bugzilla-daemon
2015-01-05 12:10 ` bugzilla-daemon
2015-01-05 13:48 ` bugzilla-daemon
2015-01-06  1:08 ` bugzilla-daemon
2015-01-06  1:42 ` bugzilla-daemon
2015-01-07  1:55 ` bugzilla-daemon
2015-01-08 13:01 ` bugzilla-daemon
2015-01-08 14:14 ` bugzilla-daemon
2015-01-09 13:46 ` bugzilla-daemon
2015-01-09 13:46 ` bugzilla-daemon
2015-01-09 19:54 ` bugzilla-daemon
2015-01-09 20:56 ` bugzilla-daemon
2015-01-09 21:19 ` bugzilla-daemon
2015-01-10 21:13 ` bugzilla-daemon
2015-01-11  1:29 ` bugzilla-daemon
2015-01-11  2:22 ` bugzilla-daemon
2015-06-04  7:47 ` bugzilla-daemon
2015-06-05 14:54 ` bugzilla-daemon
2015-06-07 10:22 ` bugzilla-daemon
2015-06-07 14:35 ` bugzilla-daemon
2015-06-07 22:12 ` bugzilla-daemon
2015-06-09 20:40 ` bugzilla-daemon
2015-06-09 21:11 ` bugzilla-daemon
2015-06-11  2:01 ` bugzilla-daemon
2015-06-11 13:56 ` bugzilla-daemon
2015-06-11 18:22 ` bugzilla-daemon
2015-06-11 18:46 ` bugzilla-daemon
2015-06-17 17:05 ` bugzilla-daemon
2015-06-17 17:18 ` bugzilla-daemon
2015-06-17 17:54 ` bugzilla-daemon
2015-06-17 19:56 ` bugzilla-daemon
2015-06-19 23:50 ` bugzilla-daemon
2015-06-21  8:59 ` bugzilla-daemon
2015-06-22 14:33 ` bugzilla-daemon
2015-07-22 17:39 ` bugzilla-daemon
2015-12-03  1:18 ` bugzilla-daemon
2015-12-03 23:25 ` bugzilla-daemon
2015-12-03 23:52 ` bugzilla-daemon
2017-09-17 12:12 ` bugzilla-daemon
2017-09-18 20:59 ` bugzilla-daemon
2017-09-19 14:46 ` bugzilla-daemon
2017-09-19 15:04 ` bugzilla-daemon
2017-09-19 17:18 ` 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-89511-13602-K6rhD6m5QA@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).