Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Bernd Lentes <bernd.lentes@helmholtz-muenchen.de>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: question to btrfs scrub
Date: Fri, 30 Jun 2023 18:16:43 +0800	[thread overview]
Message-ID: <3d208b62-efc2-afe4-e928-986dc4c53936@gmx.com> (raw)
In-Reply-To: <PR3PR04MB7340BD6CD63180053CCA023ED62AA@PR3PR04MB7340.eurprd04.prod.outlook.com>



On 2023/6/30 17:59, Bernd Lentes wrote:
>
>> -----Original Message-----
>> From: Qu Wenruo <quwenruo.btrfs@gmx.com>
>> Sent: Thursday, June 29, 2023 11:08 AM
>> To: Bernd Lentes <bernd.lentes@helmholtz-muenchen.de>; linux-btrfs <linux-
>> btrfs@vger.kernel.org>
>> Subject: Re: question to btrfs scrub
>
>> - Kernel version
> 5.14.21-150400.24.63-default
>
>> - SMART info
> ha-idg-1:/mnt/sdc1/ha-idg-1/image # smartctl -T verypermissive -a /dev/sdc
> smartctl 7.2 2021-09-14 r5237 [x86_64-linux-5.14.21-150400.24.63-default] (SUSE RPM)
> Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
>
> Read Device Identity failed: scsi error unsupported field in scsi command
>
> === START OF INFORMATION SECTION ===
> Device Model:     [No Information Found]
> Serial Number:    [No Information Found]
> Firmware Version: [No Information Found]
> Device is:        Not in smartctl database [for details use: -P showall]
> ATA Version is:   [No Information Found]
> Local Time is:    Fri Jun 30 11:52:26 2023 CEST
> SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
> SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
>                    Checking to be sure by trying SMART RETURN STATUS command.
> SMART support is: Unknown - Try option -s with argument 'on' to enable it.
> Read SMART Data failed: scsi error unsupported field in scsi command
>
> === START OF READ SMART DATA SECTION ===
> SMART Status command failed: scsi error unsupported field in scsi command
> SMART overall-health self-assessment test result: UNKNOWN!
> SMART Status, Attributes and Thresholds cannot be read.
>
> Read SMART Error Log failed: scsi error unsupported field in scsi command
>
> Read SMART Self-test Log failed: scsi error unsupported field in scsi command
>
> Selective Self-tests/Logging not supported
>
> ha-idg-1:/mnt/sdc1/ha-idg-1/image #
> ha-idg-1:/mnt/sdc1/ha-idg-1/image # smartctl -T verypermissive -s on /dev/sdc
> smartctl 7.2 2021-09-14 r5237 [x86_64-linux-5.14.21-150400.24.63-default] (SUSE RPM)
> Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
>
> Read Device Identity failed: scsi error unsupported field in scsi command
>
> SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
> SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
>                    Checking to be sure by trying SMART RETURN STATUS command.
> SMART support is: Unknown - Try option -s with argument 'on' to enable it.=== START OF ENABLE/DISABLE COMMANDS SECTION ===
> SMART Enable failed: scsi error unsupported field in scsi command
>
> SMART not available ?

That maybe caused by whatever the controller of the USB enclosure.

>
>> - HDD model
> external USB Seagate
>
>> IIRC there used to be some bug causing csum mismatch, if it's all in one file,
>> you can backup and remove the file, then set nodatacow for that file.
> bugs causing csum mismatch - Uaargh !

Your kernel is not that old AFAIK.

And I don't want to go that path unless there are enough evidence to
indicate that.

Have you figured out which file(s) are affected and what's the workload
of them?

Thanks,
Qu
> How do i set nodatacow ?
>
> Bernd
>
> Helmholtz Zentrum München – Deutsches Forschungszentrum für Gesundheit und Umwelt (GmbH)
> Ingolstädter Landstraße 1, D-85764 Neuherberg, https://www.helmholtz-munich.de
> Geschäftsführung: Prof. Dr. med. Dr. h.c. Matthias Tschöp, Daniela Sommer (komm.) | Aufsichtsratsvorsitzende: MinDir’in Prof. Dr. Veronika von Messling
> Registergericht: Amtsgericht München HRB 6466 | USt-IdNr. DE 129521671

  reply	other threads:[~2023-06-30 10:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29  8:26 question to btrfs scrub Bernd Lentes
2023-06-29  9:08 ` Qu Wenruo
2023-06-30  9:59   ` Bernd Lentes
2023-06-30 10:16     ` Qu Wenruo [this message]
2023-07-04 16:03       ` Bernd Lentes
2023-07-04 17:00         ` Bernd Lentes
2023-07-04 22:19         ` Qu Wenruo
2023-07-05  8:39           ` Bernd Lentes
2023-07-05  8:45             ` Qu Wenruo
2023-07-05 15:01               ` Bernd Lentes
2023-07-05 17:53                 ` Remi Gauvin
2023-07-06  6:23                   ` Qu Wenruo
2023-07-06 13:18                     ` Remi Gauvin
2023-07-07 21:02                       ` Bernd Lentes
2023-07-07 20:54                     ` Bernd Lentes
2023-07-08  5:08                       ` Qu Wenruo
2023-07-18 15:34                         ` Bernd Lentes
2023-07-07 20:40                   ` Bernd Lentes
2023-07-06  6:19                 ` Qu Wenruo
2023-07-06  7:04                   ` Andrei Borzenkov
2023-07-06  7:07                     ` Qu Wenruo
2023-07-07 20:48                   ` Bernd Lentes
2023-07-07 22:17                     ` Qu Wenruo
2023-06-29  9:12 ` Forza

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=3d208b62-efc2-afe4-e928-986dc4c53936@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=bernd.lentes@helmholtz-muenchen.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