linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: luvar@plaintext.sk
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	linux-ext4@vger.kernel.org, info <info@plaintext.sk>
Subject: Re: ext4 unknown problem
Date: Tue, 31 Jul 2012 11:45:32 -0500	[thread overview]
Message-ID: <50180BAC.8070607@redhat.com> (raw)
In-Reply-To: <1343355595.179511343719122536.JavaMail.root@shiva>

On 7/31/12 2:18 AM, luvar@plaintext.sk wrote:
> Hi,
> dmesg is probably useles:
> 
> Probably some logs after mounting...:
> 
> # dmesg | grep EXT
> EXT3-fs (md2): mounted filesystem with ordered data mode
> EXT3-fs (md2): using internal journal
> EXT3-fs (dm-2): using internal journal
> EXT3-fs (dm-2): mounted filesystem with ordered data mode
> EXT4-fs (dm-8): mounted filesystem with ordered data mode. Opts: (null)
> EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
> EXT4-fs (dm-12): mounted filesystem without journal. Opts: (null)
> EXT4-fs (dm-8): re-mounted. Opts: commit=0
> EXT4-fs (dm-3): re-mounted. Opts: commit=0
> EXT4-fs (dm-12): re-mounted. Opts: commit=0

^^^ um, what's that all about?

In theory, according to the docs, that's the same as the default, I guess.

and:

                } else if (token == Opt_commit) {
                        if (arg == 0)
                                arg = JBD2_DEFAULT_MAX_COMMIT_AGE;

ok, I guess it is.

> EXT4-fs (dm-28): mounted filesystem with ordered data mode. Opts: (null)
> EXT3-fs (dm-10): using internal journal
> EXT3-fs (dm-10): mounted filesystem with ordered data mode
> 
> On last few lines, there is some info about usb key used on thic pc:
> 
> # dmesg | tail -n 30
> sd 14:0:0:0: [sdg] Asking for cache data failed
> sd 14:0:0:0: [sdg] Assuming drive cache: write through
...

> Other lines from dmesg seems not relevant. Should I post them too?

Usually best to post all the data and let us sort it out, yes.

-Eric

> PS: Writing to disk from jbd2/dm-3-8 still active (iotop shows it still on top of I/O activity).
> 
> LuVar
> 
> ----- "Theodore Ts'o" <tytso@mit.edu> wrote:
> 
>> On Mon, Jul 30, 2012 at 08:26:20PM +0100, LuVar wrote:
>>> Hi,
>>> I have seriouse issue here. I have copyied about 7GB files to one of
>> my ext4 partitions and from that point of time there is sustained
>> write to that partition from jbd2/dm-3-8 process. I have lunched "sudo
>> sync" command (about day ago :) and a few hours a after sync start, I
>> have tryied to use umount on that partition... Booth of them are still
>> running...
>>>
>>> I have no serious data there, but if I could be helpfull in
>> bugreport, give me some info what to do.
>>
>> Try running the dmesg command, and see if there's anything
>> interesting
>> there.  If you're not sure if it's interesting, send it to us and we
>> can take a quick look at it.
>>
>> Regards,
>>
>> 					- Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  parent reply	other threads:[~2012-07-31 18:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <613523755.179491343719039762.JavaMail.root@shiva>
2012-07-31  7:18 ` ext4 unknown problem luvar
2012-07-31 16:34   ` Theodore Ts'o
2012-07-31 16:45   ` Eric Sandeen [this message]
2012-08-01  8:33     ` LuVar
     [not found] <1907038122.180281343977772253.JavaMail.root@shiva>
2012-08-03  7:10 ` luvar
     [not found] <927688619.179881343809505627.JavaMail.root@shiva>
2012-08-01  8:30 ` LuVar
2012-08-01 16:18   ` Theodore Ts'o
     [not found] <711984996.179701343729808563.JavaMail.root@shiva>
2012-07-31 10:18 ` Ľubomír Varga
     [not found] <805800905.179241343676287217.JavaMail.root@shiva>
2012-07-30 19:26 ` LuVar
2012-07-30 21:52   ` Theodore Ts'o

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=50180BAC.8070607@redhat.com \
    --to=sandeen@redhat.com \
    --cc=info@plaintext.sk \
    --cc=linux-ext4@vger.kernel.org \
    --cc=luvar@plaintext.sk \
    --cc=tytso@mit.edu \
    /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).