#filesystem — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #filesystem, aggregated by home.social.
-
Have published new -rc3 of #foxing ; the tl;dr is I fixed a selinux and permisions/gid:uid preservation behavior that differed from #rsync / expected outcome in the standalone fxcp tool, and did a crap-load more testing over the last month or so in real-world situations. Other than that a couple of other doc/code hygiene things only. https://codeberg.org/aenertia/foxing/releases/tag/v0.9.5-rc3 #linux #filesystem
-
Have published new -rc3 of #foxing ; the tl;dr is I fixed a selinux and permisions/gid:uid preservation behavior that differed from #rsync / expected outcome in the standalone fxcp tool, and did a crap-load more testing over the last month or so in real-world situations. Other than that a couple of other doc/code hygiene things only. https://codeberg.org/aenertia/foxing/releases/tag/v0.9.5-rc3 #linux #filesystem
-
Have published new -rc3 of #foxing ; the tl;dr is I fixed a selinux and permisions/gid:uid preservation behavior that differed from #rsync / expected outcome in the standalone fxcp tool, and did a crap-load more testing over the last month or so in real-world situations. Other than that a couple of other doc/code hygiene things only. https://codeberg.org/aenertia/foxing/releases/tag/v0.9.5-rc3 #linux #filesystem
-
Have published new -rc3 of #foxing ; the tl;dr is I fixed a selinux and permisions/gid:uid preservation behavior that differed from #rsync / expected outcome in the standalone fxcp tool, and did a crap-load more testing over the last month or so in real-world situations. Other than that a couple of other doc/code hygiene things only. https://codeberg.org/aenertia/foxing/releases/tag/v0.9.5-rc3 #linux #filesystem
-
Have published new -rc3 of #foxing ; the tl;dr is I fixed a selinux and permisions/gid:uid preservation behavior that differed from #rsync / expected outcome in the standalone fxcp tool, and did a crap-load more testing over the last month or so in real-world situations. Other than that a couple of other doc/code hygiene things only. https://codeberg.org/aenertia/foxing/releases/tag/v0.9.5-rc3 #linux #filesystem
-
#Development #Reviews
The new yet familiar CodePen 2.0 · How the popular code editor has matured https://ilo.im/16euj8_____
#CodeEditor #Versioning #Deployments #BlocksUI #FileSystem #WebDev #Frontend #HTML #CSS #JavaScript -
#Development #Reviews
The new yet familiar CodePen 2.0 · How the popular code editor has matured https://ilo.im/16euj8_____
#CodeEditor #Versioning #Deployments #BlocksUI #FileSystem #WebDev #Frontend #HTML #CSS #JavaScript -
#Development #Reviews
The new yet familiar CodePen 2.0 · How the popular code editor has matured https://ilo.im/16euj8_____
#CodeEditor #Versioning #Deployments #BlocksUI #FileSystem #WebDev #Frontend #HTML #CSS #JavaScript -
#Development #Reviews
The new yet familiar CodePen 2.0 · How the popular code editor has matured https://ilo.im/16euj8_____
#CodeEditor #Versioning #Deployments #BlocksUI #FileSystem #WebDev #Frontend #HTML #CSS #JavaScript -
🥝 kiwifs/kiwifs
Markdown filesystem for agents and teams.
Turns markdown files into a searchable, versioned filesystem with a built-in web UI and agent integration
⭐ Stars: 620
📅 Last Update: Jul 22, 2026https://github.com/kiwifs/kiwifs
#selfhosted #homelab #selfhost #selfhosting #opensource #markdown #filesystem
-
🥝 kiwifs/kiwifs
Markdown filesystem for agents and teams.
Turns markdown files into a searchable, versioned filesystem with a built-in web UI and agent integration
⭐ Stars: 620
📅 Last Update: Jul 22, 2026https://github.com/kiwifs/kiwifs
#selfhosted #homelab #selfhost #selfhosting #opensource #markdown #filesystem
-
🥝 kiwifs/kiwifs
Markdown filesystem for agents and teams.
Turns markdown files into a searchable, versioned filesystem with a built-in web UI and agent integration
⭐ Stars: 620
📅 Last Update: Jul 22, 2026https://github.com/kiwifs/kiwifs
#selfhosted #homelab #selfhost #selfhosting #opensource #markdown #filesystem
-
#TIL that the #FAT #filesystem doesn't really store anywhere whether it's #FAT12, #FAT16 and #FAT32. What you're supposed to do is to look at the number of clusters, and determine which range it falls into. More specifically, you're supposed to look at the partition size and divide it by the number of sectors per cluster (which is stored in consistent position irrespective of FAT type).
The obvious implication of that is that the volume sizes are limited by possible cluster size ranges. There's some overlap here, though: you get more clusters (and therefore use a "longer" FAT) by using a smaller cluster size, or fewer clusters by using a larger cluster size.
https://elm-chan.org/docs/fat_e.html#fat_determination
However, there's a curious trick: there's a 16-bit "FAT size" field that indicates how many sectors are used for FAT on FAT12/FAT16 filesystems. On FAT32 this field is zero (there is a separate field for 32-bit FAT size there), and apparently some tools recognize the filesystem as FAT32 in that case, irrespective of number of clusters. This is what mkfs.vfat does when you force FAT32 on a small block device.
Why did I learn all this? Because a friend tried to make a very small EFI partition and was surprised it didn't work. I was compelled to get to a bottom of this!
-
#TIL that the #FAT #filesystem doesn't really store anywhere whether it's #FAT12, #FAT16 and #FAT32. What you're supposed to do is to look at the number of clusters, and determine which range it falls into. More specifically, you're supposed to look at the partition size and divide it by the number of sectors per cluster (which is stored in consistent position irrespective of FAT type).
The obvious implication of that is that the volume sizes are limited by possible cluster size ranges. There's some overlap here, though: you get more clusters (and therefore use a "longer" FAT) by using a smaller cluster size, or fewer clusters by using a larger cluster size.
https://elm-chan.org/docs/fat_e.html#fat_determination
However, there's a curious trick: there's a 16-bit "FAT size" field that indicates how many sectors are used for FAT on FAT12/FAT16 filesystems. On FAT32 this field is zero (there is a separate field for 32-bit FAT size there), and apparently some tools recognize the filesystem as FAT32 in that case, irrespective of number of clusters. This is what mkfs.vfat does when you force FAT32 on a small block device.
Why did I learn all this? Because a friend tried to make a very small EFI partition and was surprised it didn't work. I was compelled to get to a bottom of this!
-
#TIL that the #FAT #filesystem doesn't really store anywhere whether it's #FAT12, #FAT16 and #FAT32. What you're supposed to do is to look at the number of clusters, and determine which range it falls into. More specifically, you're supposed to look at the partition size and divide it by the number of sectors per cluster (which is stored in consistent position irrespective of FAT type).
The obvious implication of that is that the volume sizes are limited by possible cluster size ranges. There's some overlap here, though: you get more clusters (and therefore use a "longer" FAT) by using a smaller cluster size, or fewer clusters by using a larger cluster size.
https://elm-chan.org/docs/fat_e.html#fat_determination
However, there's a curious trick: there's a 16-bit "FAT size" field that indicates how many sectors are used for FAT on FAT12/FAT16 filesystems. On FAT32 this field is zero (there is a separate field for 32-bit FAT size there), and apparently some tools recognize the filesystem as FAT32 in that case, irrespective of number of clusters. This is what mkfs.vfat does when you force FAT32 on a small block device.
Why did I learn all this? Because a friend tried to make a very small EFI partition and was surprised it didn't work. I was compelled to get to a bottom of this!
-
#TIL that the #FAT #filesystem doesn't really store anywhere whether it's #FAT12, #FAT16 and #FAT32. What you're supposed to do is to look at the number of clusters, and determine which range it falls into. More specifically, you're supposed to look at the partition size and divide it by the number of sectors per cluster (which is stored in consistent position irrespective of FAT type).
The obvious implication of that is that the volume sizes are limited by possible cluster size ranges. There's some overlap here, though: you get more clusters (and therefore use a "longer" FAT) by using a smaller cluster size, or fewer clusters by using a larger cluster size.
https://elm-chan.org/docs/fat_e.html#fat_determination
However, there's a curious trick: there's a 16-bit "FAT size" field that indicates how many sectors are used for FAT on FAT12/FAT16 filesystems. On FAT32 this field is zero (there is a separate field for 32-bit FAT size there), and apparently some tools recognize the filesystem as FAT32 in that case, irrespective of number of clusters. This is what mkfs.vfat does when you force FAT32 on a small block device.
Why did I learn all this? Because a friend tried to make a very small EFI partition and was surprised it didn't work. I was compelled to get to a bottom of this!
-
#TIL that the #FAT #filesystem doesn't really store anywhere whether it's #FAT12, #FAT16 and #FAT32. What you're supposed to do is to look at the number of clusters, and determine which range it falls into. More specifically, you're supposed to look at the partition size and divide it by the number of sectors per cluster (which is stored in consistent position irrespective of FAT type).
The obvious implication of that is that the volume sizes are limited by possible cluster size ranges. There's some overlap here, though: you get more clusters (and therefore use a "longer" FAT) by using a smaller cluster size, or fewer clusters by using a larger cluster size.
https://elm-chan.org/docs/fat_e.html#fat_determination
However, there's a curious trick: there's a 16-bit "FAT size" field that indicates how many sectors are used for FAT on FAT12/FAT16 filesystems. On FAT32 this field is zero (there is a separate field for 32-bit FAT size there), and apparently some tools recognize the filesystem as FAT32 in that case, irrespective of number of clusters. This is what mkfs.vfat does when you force FAT32 on a small block device.
Why did I learn all this? Because a friend tried to make a very small EFI partition and was surprised it didn't work. I was compelled to get to a bottom of this!
-
Dear Fedi, I'm looking (and have been looking) for some time for a simple way to mount a transparent local cache for a remote filesystem (preferably sshfs) that is known to be "append only" (i.e. files are never modified after creation). This seems like a very trivial task to implement with libfuse, but I haven't found anything before. Overlayfs and other kernel options seem to be overly finicky and create more issues than they solve. I might write something myself but really hoping I don't have to. Pls boost :blobcatupsidedown:
-
Dear Fedi, I'm looking (and have been looking) for some time for a simple way to mount a transparent local cache for a remote filesystem (preferably sshfs) that is known to be "append only" (i.e. files are never modified after creation). This seems like a very trivial task to implement with libfuse, but I haven't found anything before. Overlayfs and other kernel options seem to be overly finicky and create more issues than they solve. I might write something myself but really hoping I don't have to. Pls boost :blobcatupsidedown:
-
Dear Fedi, I'm looking (and have been looking) for some time for a simple way to mount a transparent local cache for a remote filesystem (preferably sshfs) that is known to be "append only" (i.e. files are never modified after creation). This seems like a very trivial task to implement with libfuse, but I haven't found anything before. Overlayfs and other kernel options seem to be overly finicky and create more issues than they solve. I might write something myself but really hoping I don't have to. Pls boost :blobcatupsidedown:
-
Dear Fedi, I'm looking (and have been looking) for some time for a simple way to mount a transparent local cache for a remote filesystem (preferably sshfs) that is known to be "append only" (i.e. files are never modified after creation). This seems like a very trivial task to implement with libfuse, but I haven't found anything before. Overlayfs and other kernel options seem to be overly finicky and create more issues than they solve. I might write something myself but really hoping I don't have to. Pls boost :blobcatupsidedown:
-
Dear Fedi, I'm looking (and have been looking) for some time for a simple way to mount a transparent local cache for a remote filesystem (preferably sshfs) that is known to be "append only" (i.e. files are never modified after creation). This seems like a very trivial task to implement with libfuse, but I haven't found anything before. Overlayfs and other kernel options seem to be overly finicky and create more issues than they solve. I might write something myself but really hoping I don't have to. Pls boost :blobcatupsidedown:
-
Open-source replacement for the Amiga's CD file system: ODFileSystem 0.6
Version 0.6 is a performance release: On the cdbench fixture (68020 -O2 release build) sequential read throughput climbs from 46,262 KiB/s to 197,673 KiB/s — a 4.3× increase (+327%) — and now runs 27% faster than the original AmigaOS 3.2.x CDFileSystem it replaces. This release also adds High Sierra, ISO 9660 Level 3, and native symlink support.
-
Open-source replacement for the Amiga's CD file system: ODFileSystem 0.6
Version 0.6 is a performance release: On the cdbench fixture (68020 -O2 release build) sequential read throughput climbs from 46,262 KiB/s to 197,673 KiB/s — a 4.3× increase (+327%) — and now runs 27% faster than the original AmigaOS 3.2.x CDFileSystem it replaces. This release also adds High Sierra, ISO 9660 Level 3, and native symlink support.
-
Open-source replacement for the Amiga's CD file system: ODFileSystem 0.6
Version 0.6 is a performance release: On the cdbench fixture (68020 -O2 release build) sequential read throughput climbs from 46,262 KiB/s to 197,673 KiB/s — a 4.3× increase (+327%) — and now runs 27% faster than the original AmigaOS 3.2.x CDFileSystem it replaces. This release also adds High Sierra, ISO 9660 Level 3, and native symlink support.
-
Open-source replacement for the Amiga's CD file system: ODFileSystem 0.6
Version 0.6 is a performance release: On the cdbench fixture (68020 -O2 release build) sequential read throughput climbs from 46,262 KiB/s to 197,673 KiB/s — a 4.3× increase (+327%) — and now runs 27% faster than the original AmigaOS 3.2.x CDFileSystem it replaces. This release also adds High Sierra, ISO 9660 Level 3, and native symlink support.
-
Open-source replacement for the Amiga's CD file system: ODFileSystem 0.6
Version 0.6 is a performance release: On the cdbench fixture (68020 -O2 release build) sequential read throughput climbs from 46,262 KiB/s to 197,673 KiB/s — a 4.3× increase (+327%) — and now runs 27% faster than the original AmigaOS 3.2.x CDFileSystem it replaces. This release also adds High Sierra, ISO 9660 Level 3, and native symlink support.
-
After 20+ years without real users, the EFS file system driver is queued for removal from the Linux kernel in version 7.3.
#LinuxKernel #EFS #FileSystem #Linux73 #OpenSource
https://meterpreter.org/linux-efs-file-system-removal/?utm_source=mastodon&utm_medium=jetpack_social
-
After 20+ years without real users, the EFS file system driver is queued for removal from the Linux kernel in version 7.3.
#LinuxKernel #EFS #FileSystem #Linux73 #OpenSource
https://meterpreter.org/linux-efs-file-system-removal/?utm_source=mastodon&utm_medium=jetpack_social
-
I'm not the only, and definitely not the first one to (re)consider the #filesystem for #database use.
The #BeFS documentation (from #HaikuOS website) clearly states - and does that - already (2004):
> "[key/value metadata attributes] add considerable power to a file system and endow the file system with many of the features normally associated with a database."
https://www.haiku-os.org/legacy-docs/practical-file-system-design.pdf
-
I'm not the only, and definitely not the first one to (re)consider the #filesystem for #database use.
The #BeFS documentation (from #HaikuOS website) clearly states - and does that - already (2004):
> "[key/value metadata attributes] add considerable power to a file system and endow the file system with many of the features normally associated with a database."
https://www.haiku-os.org/legacy-docs/practical-file-system-design.pdf
-
I'm not the only, and definitely not the first one to (re)consider the #filesystem for #database use.
The #BeFS documentation (from #HaikuOS website) clearly states - and does that - already (2004):
> "[key/value metadata attributes] add considerable power to a file system and endow the file system with many of the features normally associated with a database."
https://www.haiku-os.org/legacy-docs/practical-file-system-design.pdf
-
I'm not the only, and definitely not the first one to (re)consider the #filesystem for #database use.
The #BeFS documentation (from #HaikuOS website) clearly states - and does that - already (2004):
> "[key/value metadata attributes] add considerable power to a file system and endow the file system with many of the features normally associated with a database."
https://www.haiku-os.org/legacy-docs/practical-file-system-design.pdf
-
I'm not the only, and definitely not the first one to (re)consider the #filesystem for #database use.
The #BeFS documentation (from #HaikuOS website) clearly states - and does that - already (2004):
> "[key/value metadata attributes] add considerable power to a file system and endow the file system with many of the features normally associated with a database."
https://www.haiku-os.org/legacy-docs/practical-file-system-design.pdf
-
Can't rename "File" to "file" on an exFAT drive in Linux? Learn why case-only renames fail, how exFAT compares filenames, and the simple workaround.
Full guide here: https://ostechnix.com/why-case-only-renames-fail-exfat-linux/
#exfat #filesystem #linux #rename #troubleshooting #linuxhowto #linuxcommands #linuxbasics
-
Can't rename "File" to "file" on an exFAT drive in Linux? Learn why case-only renames fail, how exFAT compares filenames, and the simple workaround.
Full guide here: https://ostechnix.com/why-case-only-renames-fail-exfat-linux/
#exfat #filesystem #linux #rename #troubleshooting #linuxhowto #linuxcommands #linuxbasics
-
Can't rename "File" to "file" on an exFAT drive in Linux? Learn why case-only renames fail, how exFAT compares filenames, and the simple workaround.
Full guide here: https://ostechnix.com/why-case-only-renames-fail-exfat-linux/
#exfat #filesystem #linux #rename #troubleshooting #linuxhowto #linuxcommands #linuxbasics
-
Can't rename "File" to "file" on an exFAT drive in Linux? Learn why case-only renames fail, how exFAT compares filenames, and the simple workaround.
Full guide here: https://ostechnix.com/why-case-only-renames-fail-exfat-linux/
#exfat #filesystem #linux #rename #troubleshooting #linuxhowto #linuxcommands #linuxbasics
-
Can't rename "File" to "file" on an exFAT drive in Linux? Learn why case-only renames fail, how exFAT compares filenames, and the simple workaround.
Full guide here: https://ostechnix.com/why-case-only-renames-fail-exfat-linux/
#exfat #filesystem #linux #rename #troubleshooting #linuxhowto #linuxcommands #linuxbasics
-
Ah, yes, just what the world needed: a #filesystem that turns your storage into a Rube Goldberg machine 🤹♂️. Who wouldn’t want to "log-structure" their S3 buckets until they can't recognize them from a block of Swiss cheese 🧀? And let's not forget the dream of using #Docker to turn your cloud storage into a pretentious art installation that only runs in 17 easy steps! 🚀
https://www.zerofs.net/ #RubeGoldberg #cloudstorage #techhumor #HackerNews #ngated -
Ah, yes, just what the world needed: a #filesystem that turns your storage into a Rube Goldberg machine 🤹♂️. Who wouldn’t want to "log-structure" their S3 buckets until they can't recognize them from a block of Swiss cheese 🧀? And let's not forget the dream of using #Docker to turn your cloud storage into a pretentious art installation that only runs in 17 easy steps! 🚀
https://www.zerofs.net/ #RubeGoldberg #cloudstorage #techhumor #HackerNews #ngated -
Ah, yes, just what the world needed: a #filesystem that turns your storage into a Rube Goldberg machine 🤹♂️. Who wouldn’t want to "log-structure" their S3 buckets until they can't recognize them from a block of Swiss cheese 🧀? And let's not forget the dream of using #Docker to turn your cloud storage into a pretentious art installation that only runs in 17 easy steps! 🚀
https://www.zerofs.net/ #RubeGoldberg #cloudstorage #techhumor #HackerNews #ngated -
Ah, yes, just what the world needed: a #filesystem that turns your storage into a Rube Goldberg machine 🤹♂️. Who wouldn’t want to "log-structure" their S3 buckets until they can't recognize them from a block of Swiss cheese 🧀? And let's not forget the dream of using #Docker to turn your cloud storage into a pretentious art installation that only runs in 17 easy steps! 🚀
https://www.zerofs.net/ #RubeGoldberg #cloudstorage #techhumor #HackerNews #ngated -
Ah, yes, just what the world needed: a #filesystem that turns your storage into a Rube Goldberg machine 🤹♂️. Who wouldn’t want to "log-structure" their S3 buckets until they can't recognize them from a block of Swiss cheese 🧀? And let's not forget the dream of using #Docker to turn your cloud storage into a pretentious art installation that only runs in 17 easy steps! 🚀
https://www.zerofs.net/ #RubeGoldberg #cloudstorage #techhumor #HackerNews #ngated -
ZeroFS – A log-structured filesystem for S3
#HackerNews #ZeroFS #logstructured #S3 #filesystem #cloudstorage #technews
-
ZeroFS – A log-structured filesystem for S3
#HackerNews #ZeroFS #logstructured #S3 #filesystem #cloudstorage #technews
-
ZeroFS – A log-structured filesystem for S3
#HackerNews #ZeroFS #logstructured #S3 #filesystem #cloudstorage #technews
-
ZeroFS – A log-structured filesystem for S3
#HackerNews #ZeroFS #logstructured #S3 #filesystem #cloudstorage #technews
-
ZeroFS – A log-structured filesystem for S3
#HackerNews #ZeroFS #logstructured #S3 #filesystem #cloudstorage #technews
-
I am experiencing this with #OpenZFS
➜ ~ sudo zpool status -x
pool: ughetto
state: DEGRADED
status: One or more devices could not be used because the label is missing or
invalid. Sufficient replicas exist for the pool to continue
functioning in a degraded state.
action: Replace the device using 'zpool replace'.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
scan: scrub in progress since Sat Jun 27 18:44:31 2026
141G / 141G scanned, 11.8G / 141G issued at 184M/s
0B repaired, 8.39% done, 00:12:00 to go
config:
NAME STATE READ WRITE CKSUM
ughetto DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
653332104939013944 UNAVAIL 0 0 0 was /dev/sdb1
sdc ONLINE 0 0 0
cache
sda FAULTED 0 0 0 corrupted data
errors: No known data errorsThis has already happened, but at a point where I didn’t mind losing the data, so I destroyed the pool and I recreated it from scratch, with no errors. Now, I would like to try to repair the corrupted data… Any tips? I would hate it if I have to throw away the hard disk, it’s less than one year old and I have been using it only for a couple of months… Is replacing the disk my only option?
#ZFS #systemAdministration #help #sysAd #techSupport #dataLoss #storage #partition #hardDisk #HDD #Linux #filesystem #data #storage
-
I am experiencing this with #OpenZFS
➜ ~ sudo zpool status -x
pool: ughetto
state: DEGRADED
status: One or more devices could not be used because the label is missing or
invalid. Sufficient replicas exist for the pool to continue
functioning in a degraded state.
action: Replace the device using 'zpool replace'.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
scan: scrub in progress since Sat Jun 27 18:44:31 2026
141G / 141G scanned, 11.8G / 141G issued at 184M/s
0B repaired, 8.39% done, 00:12:00 to go
config:
NAME STATE READ WRITE CKSUM
ughetto DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
653332104939013944 UNAVAIL 0 0 0 was /dev/sdb1
sdc ONLINE 0 0 0
cache
sda FAULTED 0 0 0 corrupted data
errors: No known data errorsThis has already happened, but at a point where I didn’t mind losing the data, so I destroyed the pool and I recreated it from scratch, with no errors. Now, I would like to try to repair the corrupted data… Any tips? I would hate it if I have to throw away the hard disk, it’s less than one year old and I have been using it only for a couple of months… Is replacing the disk my only option?
#ZFS #systemAdministration #help #sysAd #techSupport #dataLoss #storage #partition #hardDisk #HDD #Linux #filesystem #data #storage
-
I am experiencing this with #OpenZFS
➜ ~ sudo zpool status -x
pool: ughetto
state: DEGRADED
status: One or more devices could not be used because the label is missing or
invalid. Sufficient replicas exist for the pool to continue
functioning in a degraded state.
action: Replace the device using 'zpool replace'.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
scan: scrub in progress since Sat Jun 27 18:44:31 2026
141G / 141G scanned, 11.8G / 141G issued at 184M/s
0B repaired, 8.39% done, 00:12:00 to go
config:
NAME STATE READ WRITE CKSUM
ughetto DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
653332104939013944 UNAVAIL 0 0 0 was /dev/sdb1
sdc ONLINE 0 0 0
cache
sda FAULTED 0 0 0 corrupted data
errors: No known data errorsThis has already happened, but at a point where I didn’t mind losing the data, so I destroyed the pool and I recreated it from scratch, with no errors. Now, I would like to try to repair the corrupted data… Any tips? I would hate it if I have to throw away the hard disk, it’s less than one year old and I have been using it only for a couple of months… Is replacing the disk my only option?
#ZFS #systemAdministration #help #sysAd #techSupport #dataLoss #storage #partition #hardDisk #HDD #Linux #filesystem #data #storage
-
I am experiencing this with #OpenZFS
➜ ~ sudo zpool status -x
pool: ughetto
state: DEGRADED
status: One or more devices could not be used because the label is missing or
invalid. Sufficient replicas exist for the pool to continue
functioning in a degraded state.
action: Replace the device using 'zpool replace'.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
scan: scrub in progress since Sat Jun 27 18:44:31 2026
141G / 141G scanned, 11.8G / 141G issued at 184M/s
0B repaired, 8.39% done, 00:12:00 to go
config:
NAME STATE READ WRITE CKSUM
ughetto DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
653332104939013944 UNAVAIL 0 0 0 was /dev/sdb1
sdc ONLINE 0 0 0
cache
sda FAULTED 0 0 0 corrupted data
errors: No known data errorsThis has already happened, but at a point where I didn’t mind losing the data, so I destroyed the pool and I recreated it from scratch, with no errors. Now, I would like to try to repair the corrupted data… Any tips? I would hate it if I have to throw away the hard disk, it’s less than one year old and I have been using it only for a couple of months… Is replacing the disk my only option?
#ZFS #systemAdministration #help #sysAd #techSupport #dataLoss #storage #partition #hardDisk #HDD #Linux #filesystem #data #storage
-
I am experiencing this with #OpenZFS
➜ ~ sudo zpool status -x
pool: ughetto
state: DEGRADED
status: One or more devices could not be used because the label is missing or
invalid. Sufficient replicas exist for the pool to continue
functioning in a degraded state.
action: Replace the device using 'zpool replace'.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J
scan: scrub in progress since Sat Jun 27 18:44:31 2026
141G / 141G scanned, 11.8G / 141G issued at 184M/s
0B repaired, 8.39% done, 00:12:00 to go
config:
NAME STATE READ WRITE CKSUM
ughetto DEGRADED 0 0 0
mirror-0 DEGRADED 0 0 0
653332104939013944 UNAVAIL 0 0 0 was /dev/sdb1
sdc ONLINE 0 0 0
cache
sda FAULTED 0 0 0 corrupted data
errors: No known data errorsThis has already happened, but at a point where I didn’t mind losing the data, so I destroyed the pool and I recreated it from scratch, with no errors. Now, I would like to try to repair the corrupted data… Any tips? I would hate it if I have to throw away the hard disk, it’s less than one year old and I have been using it only for a couple of months… Is replacing the disk my only option?
#ZFS #systemAdministration #help #sysAd #techSupport #dataLoss #storage #partition #hardDisk #HDD #Linux #filesystem #data #storage
-
OpenZFS is more than a filesystem. It is a filesystem and volume manager designed to simplify storage administration. #zfs #filesystem #encryption #compression
