From: Christoph Hellwig <hch@lst.de>
To: Vladislav Bolkhovitin <vst@vlnb.net>
Cc: Christoph Hellwig <hch@lst.de>, "Ted Ts'o" <tytso@mit.edu>,
Tejun Heo <tj@kernel.org>, Vivek Goyal <vgoyal@redhat.com>,
Jan Kara <jack@suse.cz>,
jaxboe@fusionio.com, James.Bottomley@suse.de,
linux-fsdevel@vger.kernel.org, linux-scsi@vger.kernel.org,
chris.mason@oracle.com, swhiteho@redhat.com,
konishi.ryusuke@lab.ntt.co.jp, linux-kernel@vger.kernel.org,
kernel-bugs@lists.ubuntu.com
Subject: Re: extfs reliability
Date: Thu, 29 Jul 2010 15:08:52 +0200 [thread overview]
Message-ID: <20100729130852.GA11852@lst.de> (raw)
In-Reply-To: <4C517B5A.3020905@vlnb.net>
On Thu, Jul 29, 2010 at 05:00:10PM +0400, Vladislav Bolkhovitin wrote:
> You can find full kernel logs starting from iSCSI load in the attachments.
>
> I already reported such issues some time ago, but my reports were not too much welcomed, so I gave up. Anyway, anybody can easily do my tests at any time. They don't need any special hardware, just 2 Linux boxes: one for iSCSI target and one for iSCSI initiator (the test box itself). But they are generic for other transports as well. You can see there's nothing iSCSI specific in the traces.
I was only talking about ext3.
next prev parent reply other threads:[~2010-07-29 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100727183546.GG7347@redhat.com>
[not found] ` <4C4FE58C.8080403@kernel.org>
[not found] ` <20100728082447.GA7668@lst.de>
[not found] ` <4C4FECFE.9040509@kernel.org>
[not found] ` <20100728085048.GA8884@lst.de>
[not found] ` <4C4FF136.5000205@kernel.org>
[not found] ` <20100728090025.GA9252@lst.de>
[not found] ` <4C4FF592.9090800@kernel.org>
[not found] ` <20100728092859.GA11096@lst.de>
[not found] ` <20100729014431.GD4506@thunk.org>
[not found] ` <20100729083142.GA30077@lst.de>
2010-07-29 13:00 ` extfs reliability Vladislav Bolkhovitin
2010-07-29 13:08 ` Christoph Hellwig [this message]
2010-07-29 14:12 ` Vladislav Bolkhovitin
2010-07-29 14:34 ` Jan Kara
2010-07-29 18:20 ` Vladislav Bolkhovitin
2010-07-29 18:49 ` Vladislav Bolkhovitin
2010-07-29 14:26 ` Jan Kara
2010-07-29 18:20 ` Vladislav Bolkhovitin
2010-07-29 18:58 ` Ted 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=20100729130852.GA11852@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@suse.de \
--cc=chris.mason@oracle.com \
--cc=jack@suse.cz \
--cc=jaxboe@fusionio.com \
--cc=kernel-bugs@lists.ubuntu.com \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=swhiteho@redhat.com \
--cc=tj@kernel.org \
--cc=tytso@mit.edu \
--cc=vgoyal@redhat.com \
--cc=vst@vlnb.net \
/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