home.social

#filesystems — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #filesystems, aggregated by home.social.

fetched live
  1. واحد ماذابيه يبعد على
    google Chrome
    لبرشة أسباب، و سبب جديد ظهر:
    google Chrome
    صبّ لواحد
    #AI #model
    يوزن 4 جيڨاوات ماغير إستشارة
    thatprivacyguy.com/blog/chrome
    ال
    #Linux #Kernel
    عندو
    #Guide
    لصبّان و إستعمال
    #Filesystems
    جدد
    git.kernel.org/pub/scm/linux/k
    مشروع في هولندا لمراكز عمل يستعملوا
    #Linux
    و ال
    #FOSS
    (المصدر بالهولندي)
    vng.nl/artikelen/digitale-werk

  2. واحد ماذابيه يبعد على
    google Chrome
    لبرشة أسباب، و سبب جديد ظهر:
    google Chrome
    صبّ لواحد
    #AI #model
    يوزن 4 جيڨاوات ماغير إستشارة
    thatprivacyguy.com/blog/chrome
    ال
    #Linux #Kernel
    عندو
    #Guide
    لصبّان و إستعمال
    #Filesystems
    جدد
    git.kernel.org/pub/scm/linux/k
    مشروع في هولندا لمراكز عمل يستعملوا
    #Linux
    و ال
    #FOSS
    (المصدر بالهولندي)
    vng.nl/artikelen/digitale-werk

  3. واحد ماذابيه يبعد على
    google Chrome
    لبرشة أسباب، و سبب جديد ظهر:
    google Chrome
    صبّ لواحد
    #AI #model
    يوزن 4 جيڨاوات ماغير إستشارة
    thatprivacyguy.com/blog/chrome
    ال
    #Linux #Kernel
    عندو
    #Guide
    لصبّان و إستعمال
    #Filesystems
    جدد
    git.kernel.org/pub/scm/linux/k
    مشروع في هولندا لمراكز عمل يستعملوا
    #Linux
    و ال
    #FOSS
    (المصدر بالهولندي)
    vng.nl/artikelen/digitale-werk

  4. واحد ماذابيه يبعد على
    google Chrome
    لبرشة أسباب، و سبب جديد ظهر:
    google Chrome
    صبّ لواحد
    #AI #model
    يوزن 4 جيڨاوات ماغير إستشارة
    thatprivacyguy.com/blog/chrome
    ال
    #Linux #Kernel
    عندو
    #Guide
    لصبّان و إستعمال
    #Filesystems
    جدد
    git.kernel.org/pub/scm/linux/k
    مشروع في هولندا لمراكز عمل يستعملوا
    #Linux
    و ال
    #FOSS
    (المصدر بالهولندي)
    vng.nl/artikelen/digitale-werk

  5. واحد ماذابيه يبعد على
    google Chrome
    لبرشة أسباب، و سبب جديد ظهر:
    google Chrome
    صبّ لواحد
    #AI #model
    يوزن 4 جيڨاوات ماغير إستشارة
    thatprivacyguy.com/blog/chrome
    ال
    #Linux #Kernel
    عندو
    #Guide
    لصبّان و إستعمال
    #Filesystems
    جدد
    git.kernel.org/pub/scm/linux/k
    مشروع في هولندا لمراكز عمل يستعملوا
    #Linux
    و ال
    #FOSS
    (المصدر بالهولندي)
    vng.nl/artikelen/digitale-werk

  6. SSD death ☠️💀

    I am busy rebuilding the data from an SSD which died all of a sudden from one moment to the next without giving any warnings in any manner in any way.

    I always monitor SMART output of SSD drives & mechanical spinners (HDD)

    I've not seen any smart output indicating imminante dead

    This drive has acted like your girlfriend when she's just not in a good mood and without explanation says nothing to you in the morning, for hours.

    This hard crash, means that the S.M.A.R.T. monitoring hardware didn't have proper Communications with the integrated circuits on the SSD.

    The drive was always powered many times a month, never left without power for more than a week or so, thus that has not been a contributing factor to the SSD catastrophic failure

    The drive itself is fairly small.

    The data on this dead SSD I've backed up on remote drives connected in JBOD format to machines which I have running remotely.

    No ZFS on my backup machines

    • I want to run ZFS native
    • that means running a BSD OS on those machines
    • that also means I will need to backup / restore all data on those drives meaning
    • I will need 200% of the used HDD / SSD space on those machines
    • I need patience for that backup
    • I need expensive extra HDD's for that project
    • I won't pay USD 300 for a USD 120 HDD

    NO ZFS under these global SSD / HDD market prices

    Sources:

    • Moi
    • man ls(1)
    • man lsd(1)
    • man cp(1)
    • man smartctl(8)
    • man zfs(8)

    #HDD #SSD #crash #no #warning #on #TV #filesystems #remote #backup #network #JBOD #SMART #programming #bacula

  7. SSD death ☠️💀

    I am busy rebuilding the data from an SSD which died all of a sudden from one moment to the next without giving any warnings in any manner in any way.

    I always monitor SMART output of SSD drives & mechanical spinners (HDD)

    I've not seen any smart output indicating imminante dead

    This drive has acted like your girlfriend when she's just not in a good mood and without explanation says nothing to you in the morning, for hours.

    This hard crash, means that the S.M.A.R.T. monitoring hardware didn't have proper Communications with the integrated circuits on the SSD.

    The drive was always powered many times a month, never left without power for more than a week or so, thus that has not been a contributing factor to the SSD catastrophic failure

    The drive itself is fairly small.

    The data on this dead SSD I've backed up on remote drives connected in JBOD format to machines which I have running remotely.

    No ZFS on my backup machines

    • I want to run ZFS native
    • that means running a BSD OS on those machines
    • that also means I will need to backup / restore all data on those drives meaning
    • I will need 200% of the used HDD / SSD space on those machines
    • I need patience for that backup
    • I need expensive extra HDD's for that project
    • I won't pay USD 300 for a USD 120 HDD

    NO ZFS under these global SSD / HDD market prices

    Sources:

    • Moi
    • man ls(1)
    • man lsd(1)
    • man cp(1)
    • man smartctl(8)
    • man zfs(8)

    #HDD #SSD #crash #no #warning #on #TV #filesystems #remote #backup #network #JBOD #SMART #programming #bacula

  8. SSD death ☠️💀

    I am busy rebuilding the data from an SSD which died all of a sudden from one moment to the next without giving any warnings in any manner in any way.

    I always monitor SMART output of SSD drives & mechanical spinners (HDD)

    I've not seen any smart output indicating imminante dead

    This drive has acted like your girlfriend when she's just not in a good mood and without explanation says nothing to you in the morning, for hours.

    This hard crash, means that the S.M.A.R.T. monitoring hardware didn't have proper Communications with the integrated circuits on the SSD.

    The drive was always powered many times a month, never left without power for more than a week or so, thus that has not been a contributing factor to the SSD catastrophic failure

    The drive itself is fairly small.

    The data on this dead SSD I've backed up on remote drives connected in JBOD format to machines which I have running remotely.

    No ZFS on my backup machines

    • I want to run ZFS native
    • that means running a BSD OS on those machines
    • that also means I will need to backup / restore all data on those drives meaning
    • I will need 200% of the used HDD / SSD space on those machines
    • I need patience for that backup
    • I need expensive extra HDD's for that project
    • I won't pay USD 300 for a USD 120 HDD

    NO ZFS under these global SSD / HDD market prices

    Sources:

    • Moi
    • man ls(1)
    • man lsd(1)
    • man cp(1)
    • man smartctl(8)
    • man zfs(8)

    #HDD #SSD #crash #no #warning #on #TV #filesystems #remote #backup #network #JBOD #SMART #programming #bacula

  9. SSD death ☠️💀

    I am busy rebuilding the data from an SSD which died all of a sudden from one moment to the next without giving any warnings in any manner in any way.

    I always monitor SMART output of SSD drives & mechanical spinners (HDD)

    I've not seen any smart output indicating imminante dead

    This drive has acted like your girlfriend when she's just not in a good mood and without explanation says nothing to you in the morning, for hours.

    This hard crash, means that the S.M.A.R.T. monitoring hardware didn't have proper Communications with the integrated circuits on the SSD.

    The drive was always powered many times a month, never left without power for more than a week or so, thus that has not been a contributing factor to the SSD catastrophic failure

    The drive itself is fairly small.

    The data on this dead SSD I've backed up on remote drives connected in JBOD format to machines which I have running remotely.

    No ZFS on my backup machines

    • I want to run ZFS native
    • that means running a BSD OS on those machines
    • that also means I will need to backup / restore all data on those drives meaning
    • I will need 200% of the used HDD / SSD space on those machines
    • I need patience for that backup
    • I need expensive extra HDD's for that project
    • I won't pay USD 300 for a USD 120 HDD

    NO ZFS under these global SSD / HDD market prices

    Sources:

    • Moi
    • man ls(1)
    • man lsd(1)
    • man cp(1)
    • man smartctl(8)
    • man zfs(8)

    #HDD #SSD #crash #no #warning #on #TV #filesystems #remote #backup #network #JBOD #SMART #programming #bacula

  10. SSD death ☠️💀

    I am busy rebuilding the data from an SSD which died all of a sudden from one moment to the next without giving any warnings in any manner in any way.

    I always monitor SMART output of SSD drives & mechanical spinners (HDD)

    I've not seen any smart output indicating imminante dead

    This drive has acted like your girlfriend when she's just not in a good mood and without explanation says nothing to you in the morning, for hours.

    This hard crash, means that the S.M.A.R.T. monitoring hardware didn't have proper Communications with the integrated circuits on the SSD.

    The drive was always powered many times a month, never left without power for more than a week or so, thus that has not been a contributing factor to the SSD catastrophic failure

    The drive itself is fairly small.

    The data on this dead SSD I've backed up on remote drives connected in JBOD format to machines which I have running remotely.

    No ZFS on my backup machines

    • I want to run ZFS native
    • that means running a BSD OS on those machines
    • that also means I will need to backup / restore all data on those drives meaning
    • I will need 200% of the used HDD / SSD space on those machines
    • I need patience for that backup
    • I need expensive extra HDD's for that project
    • I won't pay USD 300 for a USD 120 HDD

    NO ZFS under these global SSD / HDD market prices

    Sources:

    • Moi
    • man ls(1)
    • man lsd(1)
    • man cp(1)
    • man smartctl(8)
    • man zfs(8)

    #HDD #SSD #crash #no #warning #on #TV #filesystems #remote #backup #network #JBOD #SMART #programming #bacula

  11. @Thorsted @chronodm @archivist_Liz @beet_keeper Interesting article! So that's how Apple did it "back then".

    I like their idea -and believe it should be revived. But differently. RDF-based in the end.

    I claim that unlimited xattr capable #filesystems and taking "related annotated objects" seriously as default/common storage paradigm, it would evolve stable similar to, but better then DOS8.3-to-UTF+Emojis in filenames across the Internet. ❤️ ⭐

    Let's chat! You got my email?

  12. @Thorsted @chronodm @archivist_Liz @beet_keeper Interesting article! So that's how Apple did it "back then".

    I like their idea -and believe it should be revived. But differently. RDF-based in the end.

    I claim that unlimited xattr capable #filesystems and taking "related annotated objects" seriously as default/common storage paradigm, it would evolve stable similar to, but better then DOS8.3-to-UTF+Emojis in filenames across the Internet. ❤️ ⭐

    Let's chat! You got my email?

  13. @Thorsted @chronodm @archivist_Liz @beet_keeper Interesting article! So that's how Apple did it "back then".

    I like their idea -and believe it should be revived. But differently. RDF-based in the end.

    I claim that unlimited xattr capable #filesystems and taking "related annotated objects" seriously as default/common storage paradigm, it would evolve stable similar to, but better then DOS8.3-to-UTF+Emojis in filenames across the Internet. ❤️ ⭐

    Let's chat! You got my email?

  14. @Thorsted @chronodm @archivist_Liz @beet_keeper Interesting article! So that's how Apple did it "back then".

    I like their idea -and believe it should be revived. But differently. RDF-based in the end.

    I claim that unlimited xattr capable #filesystems and taking "related annotated objects" seriously as default/common storage paradigm, it would evolve stable similar to, but better then DOS8.3-to-UTF+Emojis in filenames across the Internet. ❤️ ⭐

    Let's chat! You got my email?

  15. @Thorsted @chronodm @archivist_Liz @beet_keeper Interesting article! So that's how Apple did it "back then".

    I like their idea -and believe it should be revived. But differently. RDF-based in the end.

    I claim that unlimited xattr capable #filesystems and taking "related annotated objects" seriously as default/common storage paradigm, it would evolve stable similar to, but better then DOS8.3-to-UTF+Emojis in filenames across the Internet. ❤️ ⭐

    Let's chat! You got my email?

  16. New article: Inside ZFS 🔥

    A walk through the three layers (SPA, DMU, DSL), the 128-byte block pointer that makes the whole pool a Merkle tree, the uberblock ring, and why snapshots are O(1).

    👉 internals-for-interns.com/post

    #ZFS #Filesystems

  17. New article: Inside ZFS 🔥

    A walk through the three layers (SPA, DMU, DSL), the 128-byte block pointer that makes the whole pool a Merkle tree, the uberblock ring, and why snapshots are O(1).

    👉 internals-for-interns.com/post

    #ZFS #Filesystems

  18. New article: Inside ZFS 🔥

    A walk through the three layers (SPA, DMU, DSL), the 128-byte block pointer that makes the whole pool a Merkle tree, the uberblock ring, and why snapshots are O(1).

    👉 internals-for-interns.com/post

    #ZFS #Filesystems

  19. Spent the weekend deep in ZFS internals 🤓

    Next up in the filesystems series: how a 128-byte block pointer turns the entire pool into a Merkle tree, and why snapshots are basically free (just copy a pointer + stamp a TXG).

    SPA ↔ DMU ↔ DSL, uberblocks, vdevs, ARC, ZIL.

    Drops Monday

    #ZFS #Filesystems

  20. Spent the weekend deep in ZFS internals 🤓

    Next up in the filesystems series: how a 128-byte block pointer turns the entire pool into a Merkle tree, and why snapshots are basically free (just copy a pointer + stamp a TXG).

    SPA ↔ DMU ↔ DSL, uberblocks, vdevs, ARC, ZIL.

    Drops Monday

    #ZFS #Filesystems

  21. Spent the weekend deep in ZFS internals 🤓

    Next up in the filesystems series: how a 128-byte block pointer turns the entire pool into a Merkle tree, and why snapshots are basically free (just copy a pointer + stamp a TXG).

    SPA ↔ DMU ↔ DSL, uberblocks, vdevs, ARC, ZIL.

    Drops Monday

    #ZFS #Filesystems

  22. #AWS introduced #S3Files, letting users mount an Amazon S3 bucket and access data through a standard file system interface.

    Applications can read and write files with standard file operations, while the system translates them into S3 requests - allowing compute services to work directly with S3-stored data.

    Find out more: bit.ly/4mGE3Vy

    #InfoQ #CloudComputing #FileSystems #DataStorage

  23. #AWS introduced #S3Files, letting users mount an Amazon S3 bucket and access data through a standard file system interface.

    Applications can read and write files with standard file operations, while the system translates them into S3 requests - allowing compute services to work directly with S3-stored data.

    Find out more: bit.ly/4mGE3Vy

    #InfoQ #CloudComputing #FileSystems #DataStorage

  24. #AWS introduced #S3Files, letting users mount an Amazon S3 bucket and access data through a standard file system interface.

    Applications can read and write files with standard file operations, while the system translates them into S3 requests - allowing compute services to work directly with S3-stored data.

    Find out more: bit.ly/4mGE3Vy

    #InfoQ #CloudComputing #FileSystems #DataStorage

  25. #AWS introduced #S3Files, letting users mount an Amazon S3 bucket and access data through a standard file system interface.

    Applications can read and write files with standard file operations, while the system translates them into S3 requests - allowing compute services to work directly with S3-stored data.

    Find out more: bit.ly/4mGE3Vy

    #InfoQ #CloudComputing #FileSystems #DataStorage

  26. introduced , letting users mount an Amazon S3 bucket and access data through a standard file system interface.

    Applications can read and write files with standard file operations, while the system translates them into S3 requests - allowing compute services to work directly with S3-stored data.

    Find out more: bit.ly/4mGE3Vy

  27. Kent Overstreet released Bcachefs 1.38 on Saturday from DKMS (an out-of-tree kernel module path), the second post-mainline-removal release. The on-mount allocator deadlock that stuck users through three releases is finally fixed. Journal pipelining moves from a 16-entry cap to 256. An accidental quadratic snapshot-table grow path is gone. Mainline status moves committee meetings. The 1.38 changelog moves your fleet off the deadlock blocking writes today.

    #Linux #FOSS #Filesystems #OpenSource

  28. Kent Overstreet released Bcachefs 1.38 on Saturday from DKMS (an out-of-tree kernel module path), the second post-mainline-removal release. The on-mount allocator deadlock that stuck users through three releases is finally fixed. Journal pipelining moves from a 16-entry cap to 256. An accidental quadratic snapshot-table grow path is gone. Mainline status moves committee meetings. The 1.38 changelog moves your fleet off the deadlock blocking writes today.

    #Linux #FOSS #Filesystems #OpenSource

  29. I'm in love with Linux.

    It just decompressed a 2GB zip file in 2 seconds.

    The same file in Windows is still decompressing 🤣

    #Linux #FOSS #OSS #OpenSource #Zip #FileSystem #FileSystems

  30. I'm in love with Linux.

    It just decompressed a 2GB zip file in 2 seconds.

    The same file in Windows is still decompressing 🤣

    #Linux #FOSS #OSS #OpenSource #Zip #FileSystem #FileSystems

  31. I'm in love with Linux.

    It just decompressed a 2GB zip file in 2 seconds.

    The same file in Windows is still decompressing 🤣

    #Linux #FOSS #OSS #OpenSource #Zip #FileSystem #FileSystems

  32. I'm in love with Linux.

    It just decompressed a 2GB zip file in 2 seconds.

    The same file in Windows is still decompressing 🤣

    #Linux #FOSS #OSS #OpenSource #Zip #FileSystem #FileSystems

  33. I'm in love with Linux.

    It just decompressed a 2GB zip file in 2 seconds.

    The same file in Windows is still decompressing 🤣

    #Linux #FOSS #OSS #OpenSource #Zip #FileSystem #FileSystems

  34. You can read fast file system drives in Linux, just modprobe the proper kernel module

    FFS is not UFS with extras, read the link provided if you are interested

    @rl_dane @OpenComputeDesign @moses_izumi

    #RetroComputing #Amiga #RetroGaming #FFS #filesystems #programming #M68k

  35. You can read fast file system drives in Linux, just modprobe the proper kernel module

    FFS is not UFS with extras, read the link provided if you are interested

    @rl_dane @OpenComputeDesign @moses_izumi

    #RetroComputing #Amiga #RetroGaming #FFS #filesystems #programming #M68k

  36. You can read fast file system drives in Linux, just modprobe the proper kernel module

    FFS is not UFS with extras, read the link provided if you are interested

    @rl_dane @OpenComputeDesign @moses_izumi

    #RetroComputing #Amiga #RetroGaming #FFS #filesystems #programming #M68k

  37. You can read fast file system drives in Linux, just modprobe the proper kernel module

    FFS is not UFS with extras, read the link provided if you are interested

    @rl_dane @OpenComputeDesign @moses_izumi

    #RetroComputing #Amiga #RetroGaming #FFS #filesystems #programming #M68k

  38. You can read fast file system drives in Linux, just modprobe the proper kernel module

    FFS is not UFS with extras, read the link provided if you are interested

    @rl_dane @OpenComputeDesign @moses_izumi

    #RetroComputing #Amiga #RetroGaming #FFS #filesystems #programming #M68k

  39. In this week's installment of my #wikiversity #os course, we are exploring #filesystems. The lecture covers the basics of file systems and takes a somewhat deep look at FAT32, and the activity has you implement a file system that I designed called "The Brittle File System." (As the name implies, you probably shouldn't store anything important in it!)

    en.wikiversity.org/wiki/Operat