On Fri, Jan 15, 2021 at 1:17 AM Tim via users
wrote:
>
> On Thu, 2021-01-14 at 19:56 -0700, Chris Murphy wrote:
> > Clearly those lifetime numbers are bogus, as well as sometimes
> > reporting a lower lifetime value than the test before it. It's
> > getting younger!! My SSD found the fountain of
On Thu, 2021-01-14 at 19:56 -0700, Chris Murphy wrote:
> Clearly those lifetime numbers are bogus, as well as sometimes
> reporting a lower lifetime value than the test before it. It's
> getting younger!! My SSD found the fountain of youth!
Or is it counting down to its death, instead?
--
On Thu, Jan 14, 2021 at 6:58 PM Gordon Messmer wrote:
>
> On 1/13/21 11:21 PM, Chris Murphy wrote:
> > 548 hours is not an old drive. It shouldn't have any write errors. But
> > as a drive ages there might be some and they should be handled
> > transparently and not affect any other operation.
On 1/13/21 11:21 PM, Chris Murphy wrote:
548 hours is not an old drive. It shouldn't have any write errors. But
as a drive ages there might be some and they should be handled
transparently and not affect any other operation. Something is
definitely wrong that there are write errors followed by
On 1/13/21 10:41 AM, Sreyan Chakravarty wrote:
Here is the output of:
# smartctl -Ax /dev/sda
https://pastebin.com/raw/GrgrQrSf
I have no idea what it means.
Error 5 [0] occurred at disk power-on lifetime: 1399 hours (58 days + 7 hours)
When the command that caused the error occurred,
On Wed, 2021-01-13 at 23:53 -0700, Chris Murphy wrote:
> Another possibility is power supply. Either brown outs or noisy
> incoming power. Or even made noisy by a power supply.
Don't discount cabling, either.
If connectors don't fit well, that can easily lead to failures from the
tiniest of
On 1/14/21 12:21 AM, Chris Murphy wrote:
548 hours is not an old drive.
Just under 23 days, not old at all.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of
On Wed, Jan 13, 2021 at 1:09 PM Sreyan Chakravarty wrote:
>
> On Tue, Jan 12, 2021 at 9:04 AM Chris Murphy wrote:
> >
> > Because of the --init-csum-tree failure i'm a bit concerned that it's
> > possible the --repair step didn't completely repair things. So... just
> > keep important things
On Wed, Jan 13, 2021 at 6:02 AM George N. White III wrote:
> Your drive has been used for 1671 hours, and
> 1491 power-on cycles. Mechanical device wear is often highest at startup,
> so this is probably getting close to the design lifetime of a consumer laptop
> HDD.
I missed that this is a
On Wed, Jan 13, 2021 at 2:41 AM Sreyan Chakravarty wrote:
>
> On Tue, Jan 12, 2021 at 9:16 AM Chris Murphy wrote:
> >
> >
> > -x has more information that might be relevant including firmware
> > revision and some additional logs for recent drive reported errors
> > which usually are benign. But
On Wed, Jan 13, 2021 at 2:36 AM Sreyan Chakravarty wrote:
>
> 1) Is it possible there is nothing wrong with my drive, but there is
> something with my BIOS/HDD Firmware ? May be my firmware is not
> capable of BTRFS's stringent write requirements ?
The sample size is too small to know for sure
On Tue, Jan 12, 2021 at 9:04 AM Chris Murphy wrote:
>
> Because of the --init-csum-tree failure i'm a bit concerned that it's
> possible the --repair step didn't completely repair things. So... just
> keep important things backed up. Top priority. If you told me you hate
> your data then I
On 1/13/21 12:36 AM, Sreyan Chakravarty wrote:
I am fully open to the fact that there may be something wrong with my HDD.
But it is difficult to believe that, since this laptop is from 2016
and I had been using Windows 10 on it for a long time and saw no
problems.
None that you know of.
On Wed, 2021-01-13 at 14:06 +0530, Sreyan Chakravarty wrote:
> I am fully open to the fact that there may be something wrong with my
> HDD. But it is difficult to believe that, since this laptop is from
> 2016 and I had been using Windows 10 on it for a long time and saw no
> problems.
Faults can
On Wed, 13 Jan 2021 at 05:41, Sreyan Chakravarty wrote:
> On Tue, Jan 12, 2021 at 9:16 AM Chris Murphy
> wrote:
> >
> >
> > -x has more information that might be relevant including firmware
> > revision and some additional logs for recent drive reported errors
> > which usually are benign. But
On Tue, Jan 12, 2021 at 9:16 AM Chris Murphy wrote:
>
>
> -x has more information that might be relevant including firmware
> revision and some additional logs for recent drive reported errors
> which usually are benign. But might be clues.
>
> These two attributes I'm not familiar with
> 187
On Tue, Jan 12, 2021 at 11:05 PM Chris Murphy wrote:
>
>
> Short version: Josef (Btrfs dev) and I agree there's probably
> something wrong with the drive. The advice is to replace it, just
> because trying to investigate further isn't worth your time, and also
> necessarily puts your data at
On Tue, Jan 12, 2021 at 8:52 AM Tom Horsley wrote:
>
> Not to worry! I read that bcachefs is finally making it into
> the linux kernel, so real soon now it will be the new shiny object
> and btrfs will be obsolete :-).
> ___
Let's hope it does a better
On Tue, Jan 12, 2021 at 9:22 AM Gordon Messmer wrote:
>
> https://listi.jpberlin.de/pipermail/smartmontools-support/2020-November/000559.html
>
> Your message indicated a sequence of errors that look like write
> failures, which sounds a lot like the problem that Chris described with
> your
On Tue, Jan 12, 2021 at 9:04 AM Chris Murphy wrote:
>
>
> We should talk about a backup plan in another thread :D In my own
> case, I never need them, but I have 1/2 dozen completely independent
> backups, because I hate my data and I'm constantly trying to destroy
> it. (This is turning into a
On Mon, Jan 11, 2021 at 12:24 AM Sreyan Chakravarty wrote:
>
> On Sun, Jan 10, 2021 at 3:10 AM Chris Murphy wrote:
> > Sreyan, is the drive that this file system is on the same drive as in
> > this reported thread?
> >
On 1/11/21 11:02 AM, Sreyan Chakravarty wrote:
something wrong with my HDD but the guys on the mailing list told me I
did not have to worry.
https://listi.jpberlin.de/pipermail/smartmontools-support/2020-November/000560.html
On Mon, Jan 11, 2021 at 12:02 PM Sreyan Chakravarty wrote:
>
> On Tue, Jan 12, 2021 at 12:02 AM Matthew Miller
> wrote:
> >
> >
> > Well, another way of saying that is "I wasn't having problems but now I have
> > them", which isn't super-surprising with a hard drive. What does smartctl
> > tell
On Mon, Jan 11, 2021 at 11:55 AM Sreyan Chakravarty wrote:
>
> Actually it is me who should be thanking you for not giving up.
>
> For me giving up was not an option since that would involve me losing
> all my data.
No problem!
We should talk about a backup plan in another thread :D In my own
On Mon, 11 Jan 2021 20:14:04 -0700
Chris Murphy wrote:
> The #1 reason they don't get caught and set
> free, is tester exhaustion. This is a reasonable outcome. People have
> better things to do than debug stuff. But it's sometimes a necessary
> effort because we really are at significant
On Mon, Jan 11, 2021 at 11:30 AM Sreyan Chakravarty wrote:
>
> On Mon, Jan 11, 2021 at 10:55 PM Matthew Miller
> wrote:
> >
> > On Mon, Jan 11, 2021 at 12:54:07PM +0530, Sreyan Chakravarty wrote:
> > > > Sreyan, is the drive that this file system is on the same drive as in
> > > > this reported
On Tue, Jan 12, 2021 at 12:02 AM Matthew Miller
wrote:
>
>
> Well, another way of saying that is "I wasn't having problems but now I have
> them", which isn't super-surprising with a hard drive. What does smartctl
> tell you about the drive's self-tests?
>
Well I provided this info at the
On Tue, Jan 12, 2021 at 12:24 AM Sreyan Chakravarty wrote:
>
> On Sat, Jan 9, 2021 at 11:55 AM Chris Murphy wrote:
> >
> >
> > So thanks
> > for not giving up.
> >
>
> Actually it is me who should be thanking you for not giving up.
>
> For me giving up was not an option since that would involve
On Sat, Jan 9, 2021 at 11:55 AM Chris Murphy wrote:
>
>
> So thanks
> for not giving up.
>
Actually it is me who should be thanking you for not giving up.
For me giving up was not an option since that would involve me losing
all my data.
Thank you again for your time and patience, others
On Mon, Jan 11, 2021 at 10:55 PM Matthew Miller
wrote:
>
> On Mon, Jan 11, 2021 at 12:54:07PM +0530, Sreyan Chakravarty wrote:
> > > Sreyan, is the drive that this file system is on the same drive as in
> > > this reported thread?
> > >
On Mon, Jan 11, 2021 at 12:54:07PM +0530, Sreyan Chakravarty wrote:
> > Sreyan, is the drive that this file system is on the same drive as in
> > this reported thread?
> >
On Mon, 11 Jan 2021, 3:29 pm Chris Murphy, wrote:
>
>
> On Mon, Jan 11, 2021, 12:22 AM Sreyan Chakravarty
> wrote:
>
>> On Sun, Jan 10, 2021 at 2:11 AM Matthew Miller
>> wrote:
>> >
>> > On Sun, Jan 10, 2021 at 02:01:56AM +0530, Sreyan Chakravarty wrote:
>> > > If I don't have ECC does that
On Mon, Jan 11, 2021, 12:22 AM Sreyan Chakravarty
wrote:
> On Sun, Jan 10, 2021 at 2:11 AM Matthew Miller
> wrote:
> >
> > On Sun, Jan 10, 2021 at 02:01:56AM +0530, Sreyan Chakravarty wrote:
> > > If I don't have ECC does that mean I shouldn't use BTRFS ?
> >
> > The chance of data corruption
On Sun, Jan 10, 2021 at 3:10 AM Chris Murphy wrote:
>
> No. And also, this problem is not related to a memory error. In this
> case multiple writes from one commit are missing. They just didn't
> make it to stable media. There isn't enough information to know why.
> We might get lucky and find
On Sun, Jan 10, 2021 at 2:11 AM Matthew Miller wrote:
>
> On Sun, Jan 10, 2021 at 02:01:56AM +0530, Sreyan Chakravarty wrote:
> > If I don't have ECC does that mean I shouldn't use BTRFS ?
>
> The chance of data corruption due to memory errors is rare, but it does
> happen. If it happened and you
On Sat, Jan 9, 2021 at 1:32 PM Sreyan Chakravarty wrote:
>
> If I don't have ECC does that mean I shouldn't use BTRFS ?
No. And also, this problem is not related to a memory error. In this
case multiple writes from one commit are missing. They just didn't
make it to stable media. There isn't
On Sun, Jan 10, 2021 at 02:01:56AM +0530, Sreyan Chakravarty wrote:
> If I don't have ECC does that mean I shouldn't use BTRFS ?
The chance of data corruption due to memory errors is rare, but it does
happen. If it happened and you were using ext4, the result wouldn't be that
everything is fine,
On Sun, Jan 10, 2021 at 1:43 AM Gordon Messmer wrote:
>
> On 1/9/21 11:49 AM, Sreyan Chakravarty wrote:
> > https://askubuntu.com/a/391178/628460
> > Will the above work in telling me if I have ECC RAM ?
>
> It should:
>
> # lshw -C memory
> ...
>*-memory
> description: System Memory
On 1/9/21 11:49 AM, Sreyan Chakravarty wrote:
https://askubuntu.com/a/391178/628460
Will the above work in telling me if I have ECC RAM ?
It should:
# lshw -C memory
...
*-memory
description: System Memory
physical id: 27
slot: System board or motherboard
size:
On Sun, Jan 10, 2021 at 12:22 AM Gordon Messmer
wrote:
>
> On 1/9/21 9:09 AM, Sreyan Chakravarty wrote:
> > I mean, this is the reason I keep complaining that BTRFS is not stable
> > enough.
> > ...
> > So is this a problem of my machine/firmware or a problem in BTRFS itself ?
>
>
> Since I
On Sun, Jan 10, 2021 at 12:22 AM Gordon Messmer
wrote:
>
> On 1/9/21 9:09 AM, Sreyan Chakravarty wrote:
> > I mean, this is the reason I keep complaining that BTRFS is not stable
> > enough.
> > ...
> > So is this a problem of my machine/firmware or a problem in BTRFS itself ?
>
>
> Since I
On 1/9/21 9:09 AM, Sreyan Chakravarty wrote:
I mean, this is the reason I keep complaining that BTRFS is not stable enough.
...
So is this a problem of my machine/firmware or a problem in BTRFS itself ?
Since I haven't seen it asked yet: Does this system have ECC RAM?
I don't want to
On Sat, Jan 9, 2021 at 11:10 PM Chris Murphy wrote:
>
>
>
> On Sat, Jan 9, 2021, 10:11 AM Sreyan Chakravarty wrote:
>>
>> On Sat, Jan 9, 2021 at 11:55 AM Chris Murphy wrote:
>> >
>> > 1. If you don't have a backup of important data, you should first use
>> > 'btrfs restore' as I've described in
On Sat, Jan 9, 2021, 10:11 AM Sreyan Chakravarty wrote:
> On Sat, Jan 9, 2021 at 11:55 AM Chris Murphy
> wrote:
> >
> > 1. If you don't have a backup of important data, you should first use
> > 'btrfs restore' as I've described in previous emails. The fsck should
> > fix the problem, but there
On Sat, Jan 9, 2021 at 11:55 AM Chris Murphy wrote:
>
> 1. If you don't have a backup of important data, you should first use
> 'btrfs restore' as I've described in previous emails. The fsck should
> fix the problem, but there is a chance it makes things worse. No fsck
> is guaranteed safe,
On Sat, Jan 9, 2021 at 7:34 AM Chris Murphy wrote:
>
> Strong likelihood that it can be fixed. But if the user data is
> important we should do a btrfs restore first. That's a safe read-only
> operation, does not change the file system like fsck which always has
> risk.
>
Doesn't it make more
1. If you don't have a backup of important data, you should first use
'btrfs restore' as I've described in previous emails. The fsck should
fix the problem, but there is a chance it makes things worse. No fsck
is guaranteed safe, because it's making changes to the file system.
2. Install the
On Fri, Jan 8, 2021 at 4:42 AM Sreyan Chakravarty wrote:
>
> Is there an fsck fix available for my problem ?
Yes it just got done.
>
> Can my filesystem be fixed? Or do I have to erase everything and do a
> reinstall ?
Strong likelihood that it can be fixed. But if the user data is
important
On Fri, Jan 8, 2021 at 9:59 AM Chris Murphy wrote:
>
> In the meantime, about your btrfs restore command:
>
> # btrfs restore -sxmS -D /dev/mapper/dm_crypt
> /run/media/liveuser/Backup\ Plus/restore/
>
> Try adding -i and remove -D. The -D means files aren't restored. And
> -m and -x require
On Fri, Jan 8, 2021 at 9:59 AM Chris Murphy wrote:
>
> Sorry I missed you on IRC.
No problem.
I apologize for hounding you on both IRC and this mailing list.
But I don't have any other option, no one knows what to do here.
>
> The Btrfs dev has been doing this with a devel branch, it's not in
On Thu, Jan 7, 2021 at 1:40 AM Sreyan Chakravarty wrote:
>
> Can you tell me how you are planning to use the metadata image ?
>
> Are you going to mount it with losetup and then run btrfs-check on it ?
>
> I am asking because I can perform the checks from my side.
Sorry I missed you on IRC.
The
On Tue, Jan 5, 2021 at 5:27 AM Chris Murphy wrote:
>
> On Mon, Jan 4, 2021 at 3:00 PM Chris Murphy wrote:
> >
> > Ignore the above. New plan.
> >
> > Can you clone and build this? And then do 'btrfs-image -c9 -t4 -w
> > /dev/sdXY /mnt/pathtoimagefile'
>
> New new plan, ngompa built it for us in
On Tue, Jan 5, 2021 at 5:27 AM Chris Murphy wrote:
>
> New new plan, ngompa built it for us in Fedora copr.
>
> sudo dnf install
>
On Tue, Jan 5, 2021 at 2:58 AM Chris Murphy wrote:
>
>
> What kernel version was running when this happened? (I want to know
> the kernel version running at the time of the first instance of a
> problem.)
>
The kernel version was:
5.9.14-200.fc33.x86_64
--
Regards,
Sreyan Chakravarty
On Mon, Jan 4, 2021 at 3:00 PM Chris Murphy wrote:
>
> Ignore the above. New plan.
>
> Can you clone and build this? And then do 'btrfs-image -c9 -t4 -w
> /dev/sdXY /mnt/pathtoimagefile'
New new plan, ngompa built it for us in Fedora copr.
sudo dnf install
On Mon, Jan 4, 2021 at 1:56 PM Chris Murphy wrote:
>
> On Mon, Jan 4, 2021 at 11:32 AM Sreyan Chakravarty wrote:
> > What do I do now ?
>
> Rats. Can you retry by adding -w option? In the meantime I'll report
> back to upstream and see what they recommend next.
Ignore the above. New plan.
Can
I've filed a bug for tracking.
https://bugzilla.redhat.com/show_bug.cgi?id=1912598
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On Mon, Jan 04, 2021 at 02:01:50PM -0700, Chris Murphy wrote:
> OK one way to do this is get an account at element.io and use their
> webapp (or android or ios). I still don't know how you find #fedora
> channel once you're on matrix but maybe that's obvious - probably
> something like find
On Sun, Jan 3, 2021 at 9:11 AM Sreyan Chakravarty wrote:
>
> I don't know what happened, but I just logged into my system and
> deleted some unused files in my home directory. Just some directories.
>
> Suddenly everything on my system became read only. While rebooting I
> think I saw messages
On Mon, Jan 4, 2021 at 1:56 PM Chris Murphy wrote:
>
> An alternative is matrix. We have a matrix-irc bridge in #fedora and
> pretty soon I think the plan is to switch mainly to matrix. So if you
> know about matrix then you can join #fedora - but I don't know how to
> explain it very well since
On Mon, Jan 4, 2021 at 11:32 AM Sreyan Chakravarty wrote:
>
> On Mon, Jan 4, 2021 at 10:14 PM Chris Murphy wrote:
> > transid errors like this indicate out of order writes due to drive
> > firmware not honoring file system write ordering and then getting a
> > badly timed
On Mon, Jan 4, 2021 at 10:14 PM Chris Murphy wrote:
> transid errors like this indicate out of order writes due to drive
> firmware not honoring file system write ordering and then getting a
> badly timed crash/powerfail/shutdown.
First of all thanks for your quick response.
So would I be
On Mon, Jan 4, 2021 at 6:59 AM Sreyan Chakravarty wrote:
>
> On Mon, Jan 4, 2021 at 1:16 AM Chris Murphy wrote:
> >
> > Try to mount normally, then:
>
> I am unable to mount normally :
>
> # mount -t btrfs /dev/mapper/dm_crypt /mnt/
> mount: /mnt: wrong fs type, bad option, bad superblock on
>
On Mon, Jan 4, 2021 at 1:16 AM Chris Murphy wrote:
>
> Try to mount normally, then:
I am unable to mount normally :
# mount -t btrfs /dev/mapper/dm_crypt /mnt/
mount: /mnt: wrong fs type, bad option, bad superblock on
/dev/mapper/dm_crypt, missing codepage or helper program, or other
error.
>
On Sun, Jan 3, 2021 at 11:06 PM Andrej Podzimek via users
wrote:
>
> Are you sure you are opening the right LUKS device in the live environment?
> Is the LUKS device readable (e.g. just using "cat /dev/mapper/dm_crypt >
> /dev/null")? (Does its size look right, e.g. in "lsblk -p"?) Do you get
On Mon, Jan 4, 2021 at 11:45 AM Chris Murphy wrote:
>
> By the way, fpaste is installed by default in Fedora, and it has a new
> feature: --btrfsinfo
>
> fpaste --btrfsinfo
>
> Then paste the URL here. It'll likely format way better than whatever
> MUA you're using.
>
I ran this command from the
By the way, fpaste is installed by default in Fedora, and it has a new
feature: --btrfsinfo
fpaste --btrfsinfo
Then paste the URL here. It'll likely format way better than whatever
MUA you're using.
---
Chris Murphy
___
users mailing list --
On Sun, Jan 3, 2021, 9:11 AM Sreyan Chakravarty wrote:
> Hi,
>
> I don't know what happened, but I just logged into my system and
> deleted some unused files in my home directory. Just some directories.
>
> Suddenly everything on my system became read only. While rebooting I
> think I saw
I don't know what happened, but I just logged into my system and
deleted some unused files in my home directory. Just some directories.
Suddenly everything on my system became read only. While rebooting I
think I saw messages like:
"BTRFS Error"
I booted into a live environment to restore my
On Sun, Jan 3, 2021 at 9:40 PM Sreyan Chakravarty wrote:
>
> Hi,
>
> I don't know what happened, but I just logged into my system and
> deleted some unused files in my home directory. Just some directories.
>
> Suddenly everything on my system became read only. While rebooting I
> think I saw
70 matches
Mail list logo
