From: LuVar <luvar@plaintext.sk>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, info <info@plaintext.sk>
Subject: Re: ext4 unknown problem
Date: Wed, 1 Aug 2012 09:30:39 +0100 (GMT+01:00) [thread overview]
Message-ID: <371434290.179901343809839004.JavaMail.root@shiva> (raw)
In-Reply-To: <927688619.179881343809505627.JavaMail.root@shiva>
Hi,
----- "Theodore Ts'o" <tytso@mit.edu> wrote:
> On Tue, Jul 31, 2012 at 08:18:42AM +0100, luvar@plaintext.sk wrote:
> > usb 2-4.4: USB disconnect, device number 10
>
> So what's this? Is this at all related to how you've created your
> RAID device? You haven't told us what your RAID device on dm-3 is
> composed of (i.e., what are the underlying devices).
>
My raid is on top of five physical sata disc. That usb messages are related to usb keys which I have used on that PC.
> And there were no OOPS or BUG or WARN messages in your dmesg?
>
My full dmesg is here:
http://dawn.ynet.sk/~luvar/asdf/20120801_1024_dmesg
> > PS: Writing to disk from jbd2/dm-3-8 still active (iotop shows it
> still on top of I/O activity).
>
> I'm not sure if your kernel has trace debugging enabled, or if you
> have debugfs mounted, but try this:
>
> echo 1 > /sys/kernel/debug/tracing/events/jbd2/jbd2_run_stats/enable
File does not exist... (if there is something to turn on in kernel config, I could do that for future...)
> cat /sys/kernel/debug/tracing/trace_pipe
again, file does not exist.
>
> If these commands don't work try running this command and see if it
> works then:
>
> mount -t debugfs debugfs /sys/kernel/debug
file does not exist (debug directory), but when I have tryied to mount it to /mnt/usbsticke dir, it has failed with unknown filesystem type (again, should I for future turn something on in kernel config?).
>
> Let us know if you see jbd2 activity. It's possible that sync isn't
> returning because some process is still writing to the file system,
> and if I recall correctly, Linux 3.2 didn't have some of the sync
> livelock fixes that could cause sync to not return until the file
> system had actually quieted down completely.
>
Yes, still there is activity (first few lines from iotop):
Total DISK READ: 0.00 B/s | Total DISK WRITE: 134.97 K/s
TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND
17873 be/3 root 0.00 B/s 0.00 B/s 0.00 % 64.84 % [jbd2/dm-3-8]
> Regards,
>
> - Ted
Have a nice day,
--
LuVar
next parent reply other threads:[~2012-08-01 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <927688619.179881343809505627.JavaMail.root@shiva>
2012-08-01 8:30 ` LuVar [this message]
2012-08-01 16:18 ` ext4 unknown problem Theodore Ts'o
[not found] <1907038122.180281343977772253.JavaMail.root@shiva>
2012-08-03 7:10 ` luvar
[not found] <711984996.179701343729808563.JavaMail.root@shiva>
2012-07-31 10:18 ` Ľubomír Varga
[not found] <613523755.179491343719039762.JavaMail.root@shiva>
2012-07-31 7:18 ` luvar
2012-07-31 16:34 ` Theodore Ts'o
2012-07-31 16:45 ` Eric Sandeen
2012-08-01 8:33 ` LuVar
[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=371434290.179901343809839004.JavaMail.root@shiva \
--to=luvar@plaintext.sk \
--cc=info@plaintext.sk \
--cc=linux-ext4@vger.kernel.org \
--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).