home.social

#ntfs — Public Fediverse posts

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

  1. 外付けUSBドライブの「安全な取り外し」でエラー、でもそのまま抜いて問題なし/日本マイクロソフトのWindowsサポートチームが解説
    forest.watch.impress.co.jp/doc

    #forest_watch_impress #NTFS #USB #Windows_11 #システム_ファイル #ハードウェア #Windows

  2. 外付けUSBドライブの「安全な取り外し」でエラー、でもそのまま抜いて問題なし/日本マイクロソフトのWindowsサポートチームが解説
    forest.watch.impress.co.jp/doc

    #forest_watch_impress #NTFS #USB #Windows_11 #システム_ファイル #ハードウェア #Windows

  3. 外付けUSBドライブの「安全な取り外し」でエラー、でもそのまま抜いて問題なし/日本マイクロソフトのWindowsサポートチームが解説
    forest.watch.impress.co.jp/doc

    #forest_watch_impress #NTFS #USB #Windows_11 #システム_ファイル #ハードウェア #Windows

  4. CW: langer text, pc umbau

    so, der umbau mit den neuen HDDs ist fast abgeschlossen

    ich hab jetzt 4 tage damit verschwendet herausezufinden weshalb #jellyfin nach dem kopieren aller medien von #ntfs nach #btrfs meine ganze library komplett neu einliest und alles dupliziert

    #windows nutzt nur ctime, was allerdings der timestamp für metadata change ist, als creation time - in #linux ist es btime

    und obwohl btrfs per virtiofs in der windows vm eingebunden ist und dort im explorer nur die ctime anzeigt, nimmt jellyfin trotzdem die btime

    ja, ich weiss, ich hab ein xtrem weirdes setup - aber deshalb bin ich ja gerade am umbauen
    aber halt step-by-step und nicht alles hauruck
    #homelab

  5. How to get information after a crash leading to initramfs prompt? #ntfs

    askubuntu.com/q/1566510/612

  6. How to get information after a crash leading to initramfs prompt? #ntfs

    askubuntu.com/q/1566510/612

  7. How to get information after a crash leading to initramfs prompt? #ntfs

    askubuntu.com/q/1566510/612

  8. How to get information after a crash leading to initramfs prompt? #ntfs

    askubuntu.com/q/1566510/612

  9. How to get information after a crash leading to initramfs prompt? #ntfs

    askubuntu.com/q/1566510/612

  10. @carlton @sethmlarson And does the consensus against symbolic links arise from inexperience? Windows didn't let unprivileged users create symlinks in NTFS until Windows 10 build 14972 in 2018, and even then only if developer mode is on. Instead, Windows desktop users' experience since 1995 has been with shortcuts, which operate at the shell level, not the file system level.

    #SymbolicLinks #symlink #NTFS

  11. @carlton @sethmlarson And does the consensus against symbolic links arise from inexperience? Windows didn't let unprivileged users create symlinks in NTFS until Windows 10 build 14972 in 2018, and even then only if developer mode is on. Instead, Windows desktop users' experience since 1995 has been with shortcuts, which operate at the shell level, not the file system level.

    #SymbolicLinks #symlink #NTFS

  12. @carlton @sethmlarson And does the consensus against symbolic links arise from inexperience? Windows didn't let unprivileged users create symlinks in NTFS until Windows 10 build 14972 in 2018, and even then only if developer mode is on. Instead, Windows desktop users' experience since 1995 has been with shortcuts, which operate at the shell level, not the file system level.

    #SymbolicLinks #symlink #NTFS

  13. @carlton @sethmlarson And does the consensus against symbolic links arise from inexperience? Windows didn't let unprivileged users create symlinks in NTFS until Windows 10 build 14972 in 2018, and even then only if developer mode is on. Instead, Windows desktop users' experience since 1995 has been with shortcuts, which operate at the shell level, not the file system level.

    #SymbolicLinks #symlink #NTFS

  14. @carlton @sethmlarson And does the consensus against symbolic links arise from inexperience? Windows didn't let unprivileged users create symlinks in NTFS until Windows 10 build 14972 in 2018, and even then only if developer mode is on. Instead, Windows desktop users' experience since 1995 has been with shortcuts, which operate at the shell level, not the file system level.

    #SymbolicLinks #symlink #NTFS

  15. New post on The Byte Architect:

    **Filesystem Wars: Why Your Choice of Storage is Actually a Security Move**

    This is not a “which filesystem should I use?” checklist. It is a walk through the ideas behind FFS, BFS, NTFS, ext4, ZFS, and APFS — and why storage design is never just about storage.

    Crash consistency, journaling, soft updates, CoW, snapshots, encryption, space sharing: different filesystems solve different problems, and those choices shape reliability, usability, and security.

    The real target, of course, is APFS.

    Read it here: bytearchitect.io/macos-securit

    #macOS #Apple #APFS #ZFS #ext4 #NTFS #ReverseEngineering #InfoSec #CyberSecurity

  16. New post on The Byte Architect:

    **Filesystem Wars: Why Your Choice of Storage is Actually a Security Move**

    This is not a “which filesystem should I use?” checklist. It is a walk through the ideas behind FFS, BFS, NTFS, ext4, ZFS, and APFS — and why storage design is never just about storage.

    Crash consistency, journaling, soft updates, CoW, snapshots, encryption, space sharing: different filesystems solve different problems, and those choices shape reliability, usability, and security.

    The real target, of course, is APFS.

    Read it here: bytearchitect.io/macos-securit

    #macOS #Apple #APFS #ZFS #ext4 #NTFS #ReverseEngineering #InfoSec #CyberSecurity

  17. New post on The Byte Architect:

    **Filesystem Wars: Why Your Choice of Storage is Actually a Security Move**

    This is not a “which filesystem should I use?” checklist. It is a walk through the ideas behind FFS, BFS, NTFS, ext4, ZFS, and APFS — and why storage design is never just about storage.

    Crash consistency, journaling, soft updates, CoW, snapshots, encryption, space sharing: different filesystems solve different problems, and those choices shape reliability, usability, and security.

    The real target, of course, is APFS.

    Read it here: bytearchitect.io/macos-securit

    #macOS #Apple #APFS #ZFS #ext4 #NTFS #ReverseEngineering #InfoSec #CyberSecurity

  18. New post on The Byte Architect:

    **Filesystem Wars: Why Your Choice of Storage is Actually a Security Move**

    This is not a “which filesystem should I use?” checklist. It is a walk through the ideas behind FFS, BFS, NTFS, ext4, ZFS, and APFS — and why storage design is never just about storage.

    Crash consistency, journaling, soft updates, CoW, snapshots, encryption, space sharing: different filesystems solve different problems, and those choices shape reliability, usability, and security.

    The real target, of course, is APFS.

    Read it here: bytearchitect.io/macos-securit

    #macOS #Apple #APFS #ZFS #ext4 #NTFS #ReverseEngineering #InfoSec #CyberSecurity

  19. New post on The Byte Architect:

    **Filesystem Wars: Why Your Choice of Storage is Actually a Security Move**

    This is not a “which filesystem should I use?” checklist. It is a walk through the ideas behind FFS, BFS, NTFS, ext4, ZFS, and APFS — and why storage design is never just about storage.

    Crash consistency, journaling, soft updates, CoW, snapshots, encryption, space sharing: different filesystems solve different problems, and those choices shape reliability, usability, and security.

    The real target, of course, is APFS.

    Read it here: bytearchitect.io/macos-securit

    #macOS #Apple #APFS #ZFS #ext4 #NTFS #ReverseEngineering #InfoSec #CyberSecurity

  20. 🟠️ Nouvel article sur le blog !

    Aujourd'hui je vais vous parler de la place qu'occupe réellement un 📄️ fichier ou un 📁️ dossier sur le disque de votre ordinateur. Il s'agit d'une problématique bien plus complexe qu'il n'y paraît ! 🐰️

    ➡️ blog.flozz.fr/2026/04/19/quell

    Dans cet article je vais me concentrer essentiellement sur #Windows et #NTFS car il s'agissait de mon cas d'usage, mais la problématique générale s'applique aux autres systèmes de fichiers même si leurs structures diffèrent 😄️

    #vulgarisation

  21. 🟠️ Nouvel article sur le blog !

    Aujourd'hui je vais vous parler de la place qu'occupe réellement un 📄️ fichier ou un 📁️ dossier sur le disque de votre ordinateur. Il s'agit d'une problématique bien plus complexe qu'il n'y paraît ! 🐰️

    ➡️ blog.flozz.fr/2026/04/19/quell

    Dans cet article je vais me concentrer essentiellement sur #Windows et #NTFS car il s'agissait de mon cas d'usage, mais la problématique générale s'applique aux autres systèmes de fichiers même si leurs structures diffèrent 😄️

    #vulgarisation

  22. 🟠️ Nouvel article sur le blog !

    Aujourd'hui je vais vous parler de la place qu'occupe réellement un 📄️ fichier ou un 📁️ dossier sur le disque de votre ordinateur. Il s'agit d'une problématique bien plus complexe qu'il n'y paraît ! 🐰️

    ➡️ blog.flozz.fr/2026/04/19/quell

    Dans cet article je vais me concentrer essentiellement sur #Windows et #NTFS car il s'agissait de mon cas d'usage, mais la problématique générale s'applique aux autres systèmes de fichiers même si leurs structures diffèrent 😄️

    #vulgarisation

  23. 🟠️ Nouvel article sur le blog !

    Aujourd'hui je vais vous parler de la place qu'occupe réellement un 📄️ fichier ou un 📁️ dossier sur le disque de votre ordinateur. Il s'agit d'une problématique bien plus complexe qu'il n'y paraît ! 🐰️

    ➡️ blog.flozz.fr/2026/04/19/quell

    Dans cet article je vais me concentrer essentiellement sur #Windows et #NTFS car il s'agissait de mon cas d'usage, mais la problématique générale s'applique aux autres systèmes de fichiers même si leurs structures diffèrent 😄️

    #vulgarisation

  24. 🟠️ Nouvel article sur le blog !

    Aujourd'hui je vais vous parler de la place qu'occupe réellement un 📄️ fichier ou un 📁️ dossier sur le disque de votre ordinateur. Il s'agit d'une problématique bien plus complexe qu'il n'y paraît ! 🐰️

    ➡️ blog.flozz.fr/2026/04/19/quell

    Dans cet article je vais me concentrer essentiellement sur #Windows et #NTFS car il s'agissait de mon cas d'usage, mais la problématique générale s'applique aux autres systèmes de fichiers même si leurs structures diffèrent 😄️

    #vulgarisation

  25. 🐧 Linux 7.1 核心重大更新:NTFS 驅動效能躍進

    對於雙系統使用者或伺服器管理者來說,這是 2026 年最重要的核心更新之一。Linux 7.1 對 NTFS 原生驅動架構進行了深度優化:

    🚀 效能翻倍:透過全新架構減少 CPU 開銷,讓讀寫不再卡頓。
    🛠️ 相容性強化:更完美地支援 Windows 特有的檔案系統特性。
    🛡️ 穩定救援:大幅提升對損壞分區的處理能力與掛載穩定性。

    詳細技術架構解析:
    https://2025.data-recover.com.tw/news/Linux-7-1-NTFS%E5%BE%A9%E8%88%88-%E5%8E%9F%E7%94%9F%E9%A9%85%E5%8B%95%E6%9E%B6%E6%A7%8B%E6%95%88%E8%83%BD%E8%BA%8D%E9%80%B2%E5%AE%8C%E5%85%A8%E8%A7%A3%E6%9E%90

    #Linux #Kernel71 #NTFS #資料救援 #技術分享 #tech #technews

  26. У версію ядра #Linux 7.1 включили новий драйвер #ntfs, який замінить попередній, що працював у режимі read only. 🥳

  27. Linux 7.1 finally features the improved NTFS driver!

    The current versions of Linux feature the present-time Paragon NTFS3 driver that is included in the kernel to add support for NTFS file system to it, so that users can finally mount the NTFS partitions, especially when it comes to Windows system partitions, as long as the Windows system is fully shut down.

    Prior versions of Linux included an early read-only NTFS driver that allowed you to read files from NTFS partitions but not write to them. This was a severe limitation to those who needed to write files to those partitions, especially when they needed to repair Windows installations, such as Windows XP, which uses NTFS as the default file system for the system partition.

    While the present version of Windows uses NTFS as the default file system, Linux 7.1 now features the improved NTFS driver to address the shortcomings of the two drivers. This improved NTFS driver was under development for four years under the name of “NTFS Plus” by the veteran Linux developer, Namjae Jeon, who gave us the Linux exFAT driver, and has been submitted for pull request for the Linux 7.1 merging window, as you can see here.

    Shortly afterwards, this pull request has been approved for inclusion in the source code of Linux 7.1, which means that the first release candidate of Linux 7.1, which is expected to release on April 27th, will feature the new NTFS driver. When building the kernel, you can enable this new NTFS driver to replace the existing Paragon NTFS3 driver using the NTFS_FS Kconfig variable.

    This new, resurrected NTFS driver provides full write support for NTFS file system with better stability compared to the present-time NTFS3 driver. It also provides support for mkfs (file system maker to format partitions using mkfs.ntfs) and for fsck (file system checker to check partition integrity using fsck.ntfs), and uses the modern Linux features, such as folios for improved performance and IOmap for better I/O operations. This driver can be compiled as a module, which can be found as ntfs.

    We expect that the new NTFS driver dethrone the current NTFS3 driver as soon as Linux 7.1 becomes publicly available!

    #HardDrive #Linux #news #NTFS #Tech #Technology #update
  28. Linux 7.1 finally features the improved NTFS driver!

    The current versions of Linux feature the present-time Paragon NTFS3 driver that is included in the kernel to add support for NTFS file system to it, so that users can finally mount the NTFS partitions, especially when it comes to Windows system partitions, as long as the Windows system is fully shut down.

    Prior versions of Linux included an early read-only NTFS driver that allowed you to read files from NTFS partitions but not write to them. This was a severe limitation to those who needed to write files to those partitions, especially when they needed to repair Windows installations, such as Windows XP, which uses NTFS as the default file system for the system partition.

    While the present version of Windows uses NTFS as the default file system, Linux 7.1 now features the improved NTFS driver to address the shortcomings of the two drivers. This improved NTFS driver was under development for four years under the name of “NTFS Plus” by the veteran Linux developer, Namjae Jeon, who gave us the Linux exFAT driver, and has been submitted for pull request for the Linux 7.1 merging window, as you can see here.

    Shortly afterwards, this pull request has been approved for inclusion in the source code of Linux 7.1, which means that the first release candidate of Linux 7.1, which is expected to release on April 27th, will feature the new NTFS driver. When building the kernel, you can enable this new NTFS driver to replace the existing Paragon NTFS3 driver using the NTFS_FS Kconfig variable.

    This new, resurrected NTFS driver provides full write support for NTFS file system with better stability compared to the present-time NTFS3 driver. It also provides support for mkfs (file system maker to format partitions using mkfs.ntfs) and for fsck (file system checker to check partition integrity using fsck.ntfs), and uses the modern Linux features, such as folios for improved performance and IOmap for better I/O operations. This driver can be compiled as a module, which can be found as ntfs.

    We expect that the new NTFS driver dethrone the current NTFS3 driver as soon as Linux 7.1 becomes publicly available!

    #HardDrive #Linux #news #NTFS #Tech #Technology #update
  29. Linux 7.1 finally features the improved NTFS driver!

    The current versions of Linux feature the present-time Paragon NTFS3 driver that is included in the kernel to add support for NTFS file system to it, so that users can finally mount the NTFS partitions, especially when it comes to Windows system partitions, as long as the Windows system is fully shut down.

    Prior versions of Linux included an early read-only NTFS driver that allowed you to read files from NTFS partitions but not write to them. This was a severe limitation to those who needed to write files to those partitions, especially when they needed to repair Windows installations, such as Windows XP, which uses NTFS as the default file system for the system partition.

    While the present version of Windows uses NTFS as the default file system, Linux 7.1 now features the improved NTFS driver to address the shortcomings of the two drivers. This improved NTFS driver was under development for four years under the name of “NTFS Plus” by the veteran Linux developer, Namjae Jeon, who gave us the Linux exFAT driver, and has been submitted for pull request for the Linux 7.1 merging window, as you can see here.

    Shortly afterwards, this pull request has been approved for inclusion in the source code of Linux 7.1, which means that the first release candidate of Linux 7.1, which is expected to release on April 27th, will feature the new NTFS driver. When building the kernel, you can enable this new NTFS driver to replace the existing Paragon NTFS3 driver using the NTFS_FS Kconfig variable.

    This new, resurrected NTFS driver provides full write support for NTFS file system with better stability compared to the present-time NTFS3 driver. It also provides support for mkfs (file system maker to format partitions using mkfs.ntfs) and for fsck (file system checker to check partition integrity using fsck.ntfs), and uses the modern Linux features, such as folios for improved performance and IOmap for better I/O operations. This driver can be compiled as a module, which can be found as ntfs.

    We expect that the new NTFS driver dethrone the current NTFS3 driver as soon as Linux 7.1 becomes publicly available!

    #HardDrive #Linux #news #NTFS #Tech #Technology #update
  30. Linux 7.1 finally features the improved NTFS driver!

    The current versions of Linux feature the present-time Paragon NTFS3 driver that is included in the kernel to add support for NTFS file system to it, so that users can finally mount the NTFS partitions, especially when it comes to Windows system partitions, as long as the Windows system is fully shut down.

    Prior versions of Linux included an early read-only NTFS driver that allowed you to read files from NTFS partitions but not write to them. This was a severe limitation to those who needed to write files to those partitions, especially when they needed to repair Windows installations, such as Windows XP, which uses NTFS as the default file system for the system partition.

    While the present version of Windows uses NTFS as the default file system, Linux 7.1 now features the improved NTFS driver to address the shortcomings of the two drivers. This improved NTFS driver was under development for four years under the name of “NTFS Plus” by the veteran Linux developer, Namjae Jeon, who gave us the Linux exFAT driver, and has been submitted for pull request for the Linux 7.1 merging window, as you can see here.

    Shortly afterwards, this pull request has been approved for inclusion in the source code of Linux 7.1, which means that the first release candidate of Linux 7.1, which is expected to release on April 27th, will feature the new NTFS driver. When building the kernel, you can enable this new NTFS driver to replace the existing Paragon NTFS3 driver using the NTFS_FS Kconfig variable.

    This new, resurrected NTFS driver provides full write support for NTFS file system with better stability compared to the present-time NTFS3 driver. It also provides support for mkfs (file system maker to format partitions using mkfs.ntfs) and for fsck (file system checker to check partition integrity using fsck.ntfs), and uses the modern Linux features, such as folios for improved performance and IOmap for better I/O operations. This driver can be compiled as a module, which can be found as ntfs.

    We expect that the new NTFS driver dethrone the current NTFS3 driver as soon as Linux 7.1 becomes publicly available!

    #HardDrive #Linux #news #NTFS #Tech #Technology #update