I decided to give this ST8000AS0002 a try for storing old snapshots,
although standardization for more optimal/native contol of SMR drives
is still ongoing. I saw people got it working with 3.18 kernel, so
that gave confidence.
I wanted to see if i could get it running with 4.3.0-rc6 kernel (and
I decided to give this ST8000AS0002 a try for backups / storing old
snapshots, although standardization for more optimal/native contol of
SMR drives is still ongoing. I saw people got it working with 3.18
kernel, so that gave confidence.
I wanted to see if i could get it running with 4.3.0-rc6
Hello,
I have a a single version of this drive formatted with btrfs. Its my
only btrfs drive on this machine.
I'm getting similar errors. Is there any info I can provide to help
troubleshoot this?
Is a full dmesg still wanted?
here's what I'm running-
$ uname -a
Linux machine
On Mon, Oct 12, 2015 at 06:25:52PM +0200, Henk Slager wrote:
> and looking at this spec:
> http://www.seagate.com/files/www-content/product-content/hdd-fam/seagate-archive-hdd/en-us/docs/archive-hdd-dS1834-3-1411us.pdf
>
> it seems that it is a drive-managed SMR disk. I am not sure why David
>
Hi Warren,
from your dmesg I see:
Oct 10 07:42:36 cloud.warrenhughes.net kernel: scsi 0:0:1:0:
Direct-Access ATA ST8000AS0002-1NA AR13 PQ: 0 ANSI: 5
Oct 10 07:42:36 cloud.warrenhughes.net kernel: sd 0:0:1:0: [sdb]
15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
Oct 11 23:57:56
On Mon, Oct 12, 2015 at 07:43:50AM +1300, Warren Hughes wrote:
> Hi guys, just added a new Seagate Archive 8TB drive to my BTRFS volume
> and I'm getting a tonne of errors when balancing or scrubbing.
>
> A short smartctl test reports fine, running a long one now. Will also
> run seatools from a
Yes, correct its drive managed SMR.
I have been following this bug:
https://bugzilla.kernel.org/show_bug.cgi?id=93581 for a while
As a test I compiled/installed 4.3.0-rc4 as it looks like they
reverted some kernel patches that (negatively) affect SMR.
I ran a complete balance overnight and not
I get a lot of these from both sdb and sdc
Oct 11 23:00:03 cloud.warrenhughes.net kernel: sd 0:0:1:0: [sdb]
UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Oct 11 23:00:03 cloud.warrenhughes.net kernel: sd 0:0:1:0: [sdb] Sense
Key : 0x3 [current]
Oct 11 23:00:03 cloud.warrenhughes.net
Sounds to me like this: https://bugzilla.kernel.org/show_bug.cgi?id=93581
On Mon, Oct 12, 2015 at 11:37 AM, Chris Murphy wrote:
> I get a lot of these from both sdb and sdc
>
> Oct 11 23:00:03 cloud.warrenhughes.net kernel: sd 0:0:1:0: [sdb]
> UNKNOWN(0x2003) Result:
yes indeed - referenced it in my update here
https://mail-archive.com/linux-btrfs@vger.kernel.org/msg47380.html
On 13 October 2015 at 13:04, Justin Maggard wrote:
> Sounds to me like this: https://bugzilla.kernel.org/show_bug.cgi?id=93581
>
> On Mon, Oct 12, 2015 at 11:37
Hi guys, just added a new Seagate Archive 8TB drive to my BTRFS volume
and I'm getting a tonne of errors when balancing or scrubbing.
A short smartctl test reports fine, running a long one now. Will also
run seatools from a bootable DOS USB while at work today.
Running latest firmware on my
Warren Hughes warrenhughes.net> writes:
>
> Hi guys, just added a new Seagate Archive 8TB drive to my BTRFS volume
> and I'm getting a tonne of errors when balancing or scrubbing.
>
> A short smartctl test reports fine, running a long one now. Will also
> run seatools from a bootable DOS USB
Thanks Kristan, a scrub would be great; mine appeared to be working
fine until the scrub (although I hadn't yet run a balance on it so who
knows).
I might move my 8TB onto the motherboard controller and see if the
situation improves. Will update here tonight.
Cheers, W.
On 12 October 2015 at
Hopefully this is of use - its a beast; 34MB when uncompressed
https://drive.google.com/file/d/0B74Kimpwe3nYYUZ2YTMtQXB4V1U/view?usp=sharing
On 12 October 2015 at 14:43, Chris Murphy wrote:
> Is it possible to get a complete dmesg included in the thread, or if
> it's
more info for anyone interested:
[wsh@cloud ~]$ sudo btrfs fi df /mnt/media
Data, RAID1: total=13.64TiB, used=13.61TiB
System, RAID1: total=32.00MiB, used=2.22MiB
Metadata, RAID1: total=16.00GiB, used=15.10GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
[wsh@cloud ~]$ sudo btrfs fi sh
Is it possible to get a complete dmesg included in the thread, or if
it's too big attach it to a bug report? I'm curious if there are any
libata messages, as well as the specific Btrfs messages.
---
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the
16 matches
Mail list logo