linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 810d4rk <810d4rk@gmail.com>
To: "Chris Mason" <chris.mason@oracle.com>,
	810d4rk <810d4rk@gmail.com>,
	"Jérôme Carretero" <cJ-ko@zougloub.eu>,
	sander@humilis.net, linux-btrfs@vger.kernel.org
Subject: Re: btrfs encryption problems
Date: Wed, 30 Nov 2011 22:15:25 +0000	[thread overview]
Message-ID: <CAAVfQjk+O_3uLb=DShFwV2gVnLeDzQ45ebpMidDGFXZtqXJBbQ@mail.gmail.com> (raw)
In-Reply-To: <20111130134814.GW24338@shiny>

I plugged it directly by sata and this is what I get from the 3.1 kerne=
l:

[  577.850429] ata3: exception Emask 0x10 SAct 0x0 SErr 0x4050000
action 0xe frozen
[  577.850433] ata3: irq_stat 0x00000040, connection status changed
[  577.850436] ata3: SError: { PHYRdyChg CommWake DevExch }
[  577.850443] ata3: hard resetting link
[  581.768015] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[  581.829148] ata3.00: ATA-8: WDC WD7500BPVT-22HXZT1, 01.01A01, max UD=
MA/133
[  581.829151] ata3.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 3=
1/32), AA
[  581.833146] ata3.00: configured for UDMA/133
[  581.848043] ata3: EH complete
[  581.848134] scsi 2:0:0:0: Direct-Access     ATA      WDC
WD7500BPVT-2 01.0 PQ: 0 ANSI: 5
[  581.848250] sd 2:0:0:0: [sdb] 1465149168 512-byte logical blocks:
(750 GB/698 GiB)
[  581.848253] sd 2:0:0:0: [sdb] 4096-byte physical blocks
[  581.848300] sd 2:0:0:0: [sdb] Write Protect is off
[  581.848302] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[  581.848323] sd 2:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[  581.921417]  sdb: sdb1
[  581.921642] sd 2:0:0:0: [sdb] Attached SCSI disk
[  660.040263] EXT4-fs (dm-4): VFS: Can't find ext4 filesystem

> If you plug it in directly with esata, do the IO errors go away? =C2=A0=
If so,
> please post the kernel messages from that.
>
> -chris


--=20
Thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-11-30 22:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 10:38 btrfs encryption problems 810d4rk
2011-11-23 11:09 ` Sander
2011-11-23 19:38   ` 810d4rk
2011-11-24 20:56     ` 810d4rk
2011-11-24 21:06     ` Jérôme Carretero
2011-11-24 21:43       ` 810d4rk
2011-11-24 21:54         ` Jérôme Carretero
2011-11-25 10:40           ` 810d4rk
2011-11-30 11:36             ` 810d4rk
2011-11-30 13:48             ` Chris Mason
2011-11-30 22:15               ` 810d4rk [this message]
2011-12-13  6:52                 ` 810d4rk
2011-12-13  6:56                 ` Fajar A. Nugraha
2011-12-13 11:58                   ` 810d4rk
2011-12-15 19:44                     ` 810d4rk
2011-12-15 23:49                       ` Mitch Harder
2011-12-23 14:25                         ` 810d4rk
2012-03-13 15:50                           ` 810d4rk

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='CAAVfQjk+O_3uLb=DShFwV2gVnLeDzQ45ebpMidDGFXZtqXJBbQ@mail.gmail.com' \
    --to=810d4rk@gmail.com \
    --cc=cJ-ko@zougloub.eu \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sander@humilis.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;
as well as URLs for NNTP newsgroup(s).