linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "ANEZAKI, Akira" <fireblade1230@yahoo.co.jp>
To: Gwendal Grignou <gwendal@google.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
	Mark Lord <kernel@teksavvy.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Fwd: libata-pmp patch for 3.2.x and later for eSATA Port Multiplier Sil3726
Date: Thu, 22 Mar 2012 17:16:56 +0900	[thread overview]
Message-ID: <4F6ADFF8.5000106@yahoo.co.jp> (raw)
In-Reply-To: <4F6AAC37.7040907@yahoo.co.jp>

Sorry for my poor English.
And I used wrong mail address.

(2012/03/22 13:36), ANEZAKI, Akira wrote:
> 3.2.x kernel sometimes breaks metadata and I have to fix them. I feel it
> strange and cannot understand that the kernel sometimes breaks
> metadatas/superblocks of RAIDs/file systems those don't include any HDDs
> those don't connected to any PMP.
... the kernel sometimes breaks metadata/superblock of RAID/file system.
The kernel may break them even if those don't include a HDD that is
connected to a PMP.

is correct.

Akira

  parent reply	other threads:[~2012-03-22  8:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F5ECD06.3000608@yahoo.co.jp>
2012-03-13 16:56 ` Fwd: libata-pmp patch for 3.2.x and later for eSATA Port Multiplier Sil3726 Mark Lord
2012-03-18 18:35   ` ANEZAKI, Akira
2012-03-21  9:09     ` Gwendal Grignou
2012-03-22  4:36       ` ANEZAKI, Akira
2012-03-22  8:14         ` black
2012-03-22  8:16         ` ANEZAKI, Akira [this message]
2012-03-22 12:51         ` Gwendal Grignou
2012-03-22 14:02         ` ANEZAKI, Akira
2012-03-22 16:16           ` Gwendal Grignou
2012-03-22 17:55             ` ANEZAKI, Akira
2012-03-23  5:14               ` Gwendal Grignou
2012-03-23  6:40                 ` ANEZAKI, Akira
2012-03-23  8:31                   ` Gwendal Grignou
2012-03-23  9:59                     ` ANEZAKI, Akira
2012-03-25  1:19                       ` ANEZAKI, Akira
2012-03-25 15:28                         ` Gwendal Grignou
2012-03-26  0:41                           ` ANEZAKI, Akira
2012-03-26  1:42                             ` black
2012-03-26  1:46                             ` ANEZAKI, Akira
2012-03-26  2:30                             ` ANEZAKI, Akira
2012-03-26  9:50                               ` ANEZAKI, Akira
2012-03-26 11:26                                 ` ANEZAKI, Akira
2012-03-27 11:17                                   ` Gwendal Grignou
2012-03-27 12:26                                     ` ANEZAKI, Akira
2012-03-27 13:18                                       ` ANEZAKI, Akira
2012-03-27 13:46                                         ` black
2012-03-27 14:10                                           ` ANEZAKI, Akira
2012-03-29  6:32                                         ` Gwendal Grignou
2012-03-29  7:19                                           ` ANEZAKI, Akira
2012-03-28  5:22                                     ` ANEZAKI, Akira
2012-03-28  5:29                                     ` ANEZAKI, Akira
2012-03-29  6:08                                       ` Gwendal Grignou
2012-03-29  6:27                                         ` ANEZAKI, Akira

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=4F6ADFF8.5000106@yahoo.co.jp \
    --to=fireblade1230@yahoo.co.jp \
    --cc=gwendal@google.com \
    --cc=jgarzik@pobox.com \
    --cc=kernel@teksavvy.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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).