From: Paolo Ornati <ornati-dbx96nzIXN7OeuqD6ShaSA@public.gmane.org>
To: Alexey Fisher
<bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
Cc: Kernel Testers List
<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Tejun Heo <htejun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
Subject: Re: [re] libata: blacklist NCQ on Seagate Barracuda ST380817AS
Date: Wed, 4 Mar 2009 20:31:00 +0100 [thread overview]
Message-ID: <20090304203100.35f762d9@fastwebnet.it> (raw)
In-Reply-To: <49AD9584.6070603-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
On Tue, 03 Mar 2009 21:39:32 +0100
Alexey Fisher <bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org> wrote:
> >> I use board with ICH10R south bridge, AHCI mode.
> >
> > In my case it was happening _only_ with barriers enabled (like ext3 mounted with
> > "barrier=1") or with XFS (that enables barriers by default).
> >
> > Does it survives an untar with barriers?
>
> ext4 have barriers enabled by default, but it will disable it if hdd is
> not capable to do it. So it will just return:
> JBD: barrier-based sync failed on dm-1:8 - disabling barriers
HD in question _CAN_ do barriers.
You are using device mapper, maybe it's that additional layer that
causes barriers to be disabled.
Try with a "raw" partition and see what happens.
--
Paolo Ornati
Linux 2.6.29-rc6-00305-g2450cf5 on x86_64
prev parent reply other threads:[~2009-03-04 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-01 16:28 [re] libata: blacklist NCQ on Seagate Barracuda ST380817AS Alexey Fisher
[not found] ` <49AAB796.1010709-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-03-02 7:20 ` Tejun Heo
2009-03-03 19:50 ` Paolo Ornati
[not found] ` <20090303205034.6fa9a5d5-dbx96nzIXN7OeuqD6ShaSA@public.gmane.org>
2009-03-03 20:39 ` Alexey Fisher
[not found] ` <49AD9584.6070603-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org>
2009-03-04 19:31 ` Paolo Ornati [this message]
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=20090304203100.35f762d9@fastwebnet.it \
--to=ornati-dbx96nzixn7oeuqd6shasa@public.gmane.org \
--cc=bug-track-M18mAb7Tlt0yCq4wW13eYl6hYfS7NtTn@public.gmane.org \
--cc=htejun-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).