linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: helmut@hullen.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel 3.3.4 damages filesystem (?)
Date: Mon, 7 May 2012 11:59:44 +0100	[thread overview]
Message-ID: <20120507105944.GD8938@carfax.org.uk> (raw)
In-Reply-To: <C8PBkd9uCXB@helmut.hullen.de>

[-- Attachment #1: Type: text/plain, Size: 4199 bytes --]

On Mon, May 07, 2012 at 12:46:00PM +0200, Helmut Hullen wrote:
> Hallo,
> 
> "never change a running system" ...
> 
> For some months I run btrfs unter kernel 3.2.5 and 3.2.9, without  
> problems.
> 
> Yesterday I compiled kernel 3.3.4, and this morning I started the  
> machine with this kernel. There may be some ugly problems.
> 
> Copying something into the btrfs "directory" worked well for some files,  
> and then I got error messages (I've not copied them, something with "IO  
> error" under Samba).
> 
> Rebooting the machine with kernel 3.2.9 worked, copying 1 file worked,  
> but copying more than this file didn't work. And I can't delete this  
> file.
> 
> That doesn't please me - copying more than 4 TBytes wastes time and  
> money.
> 
> =========== configuration =================
> 
> /dev/sdc1 on /srv/MM type btrfs (rw,noatime)
> 
> /dev/sdc: SAMSUNG HD204UI: 25 °C
> /dev/sdf: WDC WD30EZRX-00MMMB0: 30 °C
> /dev/sdi: WDC WD30EZRX-00MMMB0: 29 °C
> 
> Data, RAID0: total=5.29TB, used=4.29TB
> System, RAID1: total=8.00MB, used=352.00KB
> System: total=4.00MB, used=0.00
> Metadata, RAID1: total=149.00GB, used=5.00GB
> 
> Label: 'MMedia'  uuid: 9adfdc84-0fbe-431b-bcb1-cabb6a915e91
> 	Total devices 3 FS bytes used 4.29TB
> 	devid    3 size 2.73TB used 1.98TB path /dev/sdi1
> 	devid    2 size 2.73TB used 1.94TB path /dev/sdf1
> 	devid    1 size 1.82TB used 1.63TB path /dev/sdc1
> 
> Btrfs Btrfs v0.19
> 
> =================== boot messages, kernel related ==============
> 
> [boot with kernel 3.3.4]
> May  7 06:55:26 Arktur kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
> May  7 06:55:26 Arktur kernel: ata5: SError: { PHYRdyChg }
> May  7 06:55:26 Arktur kernel: ata5: hard resetting link
> May  7 06:55:31 Arktur kernel: ata5: COMRESET failed (errno=-19)
> May  7 06:55:31 Arktur kernel: ata5: reset failed (errno=-19), retrying in 6 secs
> May  7 06:55:36 Arktur kernel: ata5: hard resetting link
> May  7 06:55:38 Arktur kernel: ata5: COMRESET failed (errno=-19)
> May  7 06:55:38 Arktur kernel: ata5: reset failed (errno=-19), retrying in 9 secs
> May  7 06:55:46 Arktur kernel: ata5: hard resetting link
> May  7 06:55:47 Arktur kernel: ata5: COMRESET failed (errno=-19)
> May  7 06:55:47 Arktur kernel: ata5: reset failed (errno=-19), retrying in 34 secs
> May  7 06:56:21 Arktur kernel: ata5: hard resetting link
> May  7 06:56:22 Arktur kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> May  7 06:56:22 Arktur kernel: ata5.00: configured for UDMA/100
> May  7 06:56:22 Arktur kernel: ata5: EH complete
> May  7 07:12:07 Arktur kernel: ata5.00: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
> May  7 07:12:07 Arktur kernel: ata5: SError: { PHYRdyChg }
> May  7 07:12:07 Arktur kernel: ata5.00: failed command: WRITE DMA EXT
> May  7 07:12:07 Arktur kernel: ata5.00: cmd 35/00:00:00:62:50/00:04:5e:00:00/e0 tag 0 dma 524288 out
> May  7 07:12:07 Arktur kernel:          res d8/d8:d8:d8:d8:d8/d8:d8:d8:d8:d8/d8 Emask 0x12 (ATA bus error)
> May  7 07:12:07 Arktur kernel: ata5.00: status: { Busy }
> May  7 07:12:07 Arktur kernel: ata5.00: error: { ICRC UNC IDNF }

   This is a hardware error. You have a device that's either dead or
dying. (Given the number of errors, probably already dead).

> May  7 07:12:07 Arktur kernel: ata5: hard resetting link
> ==========================================================
> 
> The 3 btrfs disks are connected via a SiI 3114 SATA-PCI-Controller.
> Only 1 of the 3 disks seems to be damaged.
> 
> ==========================================================
> 
> Ca I repair the system? Or have I to copy it to a set of other disks?

   If you have RAID-1 or RAID-10 on both data and netadata, then you
_should_ in theory just be able to remove the dead disk (physically),
then btrfs dev add a new one, btrfs dev del missing, and balance.

   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
                        --- argc, argv, argh! ---                        

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2012-05-07 10:59 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 10:46 kernel 3.3.4 damages filesystem (?) Helmut Hullen
2012-05-07 10:58 ` Fajar A. Nugraha
2012-05-07 12:06   ` Helmut Hullen
2012-05-07 10:59 ` Hugo Mills [this message]
2012-05-07 12:15   ` Helmut Hullen
2012-05-07 13:34   ` Helmut Hullen
2012-05-07 14:05     ` Hugo Mills
2012-05-07 16:36       ` Helmut Hullen
2012-05-07 17:13         ` Felix Blanke
2012-05-07 17:52           ` Helmut Hullen
2012-05-07 18:00             ` Hugo Mills
2012-05-07 18:25               ` Helmut Hullen
2012-05-07 18:44                 ` Hugo Mills
2012-05-09 13:04                   ` failed disk (was: kernel 3.3.4 damages filesystem (?)) Helmut Hullen
2012-05-09 13:19                     ` Hugo Mills
2012-05-09 14:25               ` Helmut Hullen
2012-05-09 14:37                 ` Hugo Mills
2012-05-09 15:14                   ` failed disk Helmut Hullen
2012-05-09 15:33                     ` Hugo Mills
2012-05-09 18:49                       ` Helmut Hullen
2012-05-09 16:13                   ` failed disk (was: kernel 3.3.4 damages filesystem (?)) Ilya Dryomov
2012-05-10  2:49                   ` failed disk Helmut Hullen
2012-05-07 19:30             ` kernel 3.3.4 damages filesystem (?) Daniel Lee
2012-05-07 20:21               ` Helmut Hullen
2012-05-07 20:51                 ` Daniel Lee
2012-05-07 21:17                   ` Helmut Hullen
2012-05-07 21:27                     ` cwillu
2012-05-07 22:07                 ` Martin Steigerwald
2012-05-08  7:39                   ` Helmut Hullen
2012-05-08  7:44                     ` Fajar A. Nugraha
2012-05-08 10:00                       ` Helmut Hullen
2012-05-08 10:41                         ` Clemens Eisserer
2012-05-08 13:13                           ` Helmut Hullen
2012-05-08 13:44                             ` Felix Blanke
2012-05-08 13:52                               ` Hugo Mills
2012-05-08 16:53                               ` Helmut Hullen
2012-05-08 17:24                                 ` Felix Blanke
2012-05-08 18:29                                   ` Helmut Hullen
2012-05-08 18:41                                     ` Felix Blanke
2012-05-08 19:12                                       ` David Sterba
2012-05-08 19:34                                       ` Helmut Hullen
2012-05-08 20:02                                         ` Hugo Mills
2012-05-08 20:19                                           ` Helmut Hullen
2012-05-08 20:56                                             ` Roman Mamedov
2012-05-09 14:46                                               ` Kaspar Schleiser
2012-05-10 10:40                                                 ` Martin Steigerwald
2012-05-10 11:55                                                   ` feature request (was: kernel 3.3.4 damages filesystem (?)) Helmut Hullen
2012-05-10 19:43                                                   ` kernel 3.3.4 damages filesystem (?) Hubert Kario
2012-05-10 20:15                                                     ` Hugo Mills
2012-05-10 20:23                                                       ` Hubert Kario
2012-05-08 21:42                         ` Hubert Kario
2012-05-07 12:53 ` Liu Bo
2012-05-09 17:32 ` Duncan
2012-05-09 18:06   ` Atila

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=20120507105944.GD8938@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=helmut@hullen.de \
    --cc=linux-btrfs@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).