Hi Mark and Maxim!
>> Ext4 won't detect bitrot (silent corruption of your drive's data).
>> You'll probably wake one day with a fsck that won't be able to recover
>> some files, or worst, a completely dead drive.
>>
>> Your backups would also contain corrupted data (garbage in, garbage
>> out!).
>
Maxim Cournoyer writes:
> Raghav Gururajan writes:
>
>>> Maxim Cournoyer skribis:
>>>
I took Raghav to #btrfs last week, where with the help of gentle folks a
failing drive was established as the most likely culprit.
In other words, Btrfs checksuming capabilities helped qui
Hello Raghav,
Raghav Gururajan writes:
> Hi!
>
>> Maxim Cournoyer skribis:
>>
>>> I took Raghav to #btrfs last week, where with the help of gentle folks a
>>> failing drive was established as the most likely culprit.
>>>
>>> In other words, Btrfs checksuming capabilities helped quickly
>>> dis
Hi!
> Maxim Cournoyer skribis:
>
>> I took Raghav to #btrfs last week, where with the help of gentle folks a
>> failing drive was established as the most likely culprit.
>>
>> In other words, Btrfs checksuming capabilities helped quickly
>> discovering a hardware problem which might otherwise ha
Hi,
Maxim Cournoyer skribis:
> I took Raghav to #btrfs last week, where with the help of gentle folks a
> failing drive was established as the most likely culprit.
>
> In other words, Btrfs checksuming capabilities helped quickly
> discovering a hardware problem which might otherwise have silent
Hello,
Ludovic Courtès writes:
> Hey Raghav,
>
> Did you eventually find what went wrong? Should we close this bug or at
> least retitle it?
>
> Thanks,
> Ludo’.
I took Raghav to #btrfs last week, where with the help of gentle folks a
failing drive was established as the most likely culprit.
Hey Raghav,
Did you eventually find what went wrong? Should we close this bug or at
least retitle it?
Thanks,
Ludo’.
Hi,
On Mon, 31 Aug 2020 23:04:25 -0400
Raghav Gururajan wrote:
> Hi Danny!
>
> > Usually that means file-system corruption, which very likely was caused by a
> > hardware (disk) problem. I've had it before, and shortly after the disk
> > died.
>
> Oh no! My disk is a SSD, which is only abo
Hi Danny!
> Usually that means file-system corruption, which very likely was caused by a
> hardware (disk) problem. I've had it before, and shortly after the disk died.
Oh no! My disk is a SSD, which is only about 2 years old. Isn't that too
soon?
Btw, is there a tool to check the health of the
Hi Raghav,
On Mon, 31 Aug 2020 05:48:30 -0400
Raghav Gururajan wrote:
> Hello Guix!
>
> [1] Out of no where, when I did `guix environment foo`, I got:
>
> \note: build failure may have been caused by lack of free disk space
> builder for `/gnu/store/2ajnpcblwpgzjdhx3050qapy3li31pr5-profile.drv
Julien Lepiller writes:
> No, it's supposed to be like that. /gnu/store is mounted read-only (on
> the guix system) to prevent you from writing to it.
Very sorry for the confusion, I forgot that! (and I did not check before) :-(
>>> /dev/mapper/secondary on / type btrfs
>>> (rw,relatime,ssd,spa
No, it's supposed to be like that. /gnu/store is mounted read-only (on the guix
system) to prevent you from writing to it. The guix daemon has write access to
the store when it wants to add a new item, or garbage collect.
Le 31 août 2020 07:11:13 GMT-04:00, Giovanni Biscuolo a écrit :
>Hello Ra
Hello Raghav
when forwarding the output of commands next time, plz beware your MUS
does not reformat the relevant :-)
This seems as a system issue on your side, not a Guix bug
Raghav Gururajan writes:
>> It seems connected to a filesystem issue: can you also tell us what's
>> the output of "mo
Hi Gio!
> It seems connected to a filesystem issue: can you also tell us what's
> the output of "mount"?
none on /proc type proc (rw,relatime)
none on /dev type devtmpfs
(rw,relatime,size=3934712k,nr_inodes=983678,mode=755)
none on /sys type sysfs (rw,relatime)
/dev/mapper/secondary on / type bt
Hi Raghav
Raghav Gururajan writes:
[...]
> [2] When I redid the command 2nd time, I got:
>
> error (ignored): cannot unlink `/tmp/guix-build-profile.drv-0':
> Read-only file system
It seems connected to a filesystem issue: can you also tell us what's
the output of "mount"?
[...]
Thanks, Gio'
Hi Efraim!
> What's the output of 'df -h' and 'df -i'? There's not much change in
> error message if you're out of space or just out of inodes.
rg@secondary ~$ df -h
Filesystem Size Used Avail Use% Mounted on
none3.8G 0 3.8G 0% /dev
/dev/dm-0 120G 95G 24G 81% /
On Mon, Aug 31, 2020 at 05:48:30AM -0400, Raghav Gururajan wrote:
> Hello Guix!
>
> [1] Out of no where, when I did `guix environment foo`, I got:
>
> \note: build failure may have been caused by lack of free disk space
> builder for `/gnu/store/2ajnpcblwpgzjdhx3050qapy3li31pr5-profile.drv'
> fai
Hello Guix!
[1] Out of no where, when I did `guix environment foo`, I got:
\note: build failure may have been caused by lack of free disk space
builder for `/gnu/store/2ajnpcblwpgzjdhx3050qapy3li31pr5-profile.drv'
failed with exit code 1
[2] When I redid the command 2nd time, I got:
error (igno
18 matches
Mail list logo
