View source for File Systems/fr

<languages/>
{{UnderConstruction|Page under construction.}}
__TOC__
Cette page fournit des informations sur certains des systèmes de fichiers couramment utilisés dans Manjaro. Elle montre également où et comment ils sont utilisés. De plus amples informations sur ces systèmes de fichiers et sur d'autres peuvent être trouvées dans le wiki de ARCH.

Un système de fichiers gère l'espace sur un support de stockage (disque dur, SSD...). Il met cette espace à la disposition du système d'exploitation afin que les fichiers puissent être enregistrés et lus à nouveau. Chacun des systèmes de fichiers suivants présente des avantages et des inconvénients. Ils sont principalement développés dans un but précis et sont donc utilisés dans un certain environnement.

== Linux ==

systèmes de fichiers principalement utilisés sous Linux.

Notez que de nombreux pilotes de système de fichiers sont déjà inclus dans le noyau Linux. Vous n’aurez peut-être besoin de rien d’autre pour monter, lire ou écrire ces systèmes de fichiers. Mais il existe des packages avec des outils supplémentaires. Vous en aurez peut-être besoin pour formater, vérifier, réparer, modifier ou optimiser ces systèmes de fichiers. Donc si vous utilisez régulièrement un système de fichiers, c'est une bonne idée d'installer les outils appropriés.

=== Ext2 → Ext3 → Ext4 ===

Ext4 est actuellement le système de fichiers par défaut dans Manjaro. Il s'agit de l'évolution des systèmes de fichiers Linux les plus utilisés (Ext3, Ext2) et promet une conception améliorée, de meilleures performances, fiabilité et fonctionnalités par rapport à ses prédécesseurs.

Si vous utilisez Ext2 ou Ext3, vous pouvez convertir la partition en Ext4. Ext4 utilise la journalisation, les sommes de contrôle et les barrières d'écriture et est donc plus robuste contre les dommages.

Actuellement, Ext4 est entièrement pris en charge dans Win10 et OsX. La prise en charge d'ext4 a été intégrée depuis que WSL est inclus dans Win10 (2016).

voir [https://ext4.wiki.kernel.org/ Ext4@kernel.org], [https://wiki.archlinux.org/title/Ext4 Ext4@ARCH-wiki], [https://de.wikipedia.org/wiki/Ext4 Ext4@wikipedia] 
<br>Pour des optimisations avancées, voir [https://wiki.archlinux.org/index.php/Ext4#Improving_performance Améliorer les performances d'Ext4 @Archwiki].

====Installer====

Dans Manjaro, e2fsprogs est préinstallé

===[[Btrfs]]===

<div lang="en" dir="ltr" class="mw-content-ltr">
A modern '''C'''opy '''o'''n '''W'''rite filesystem for Linux aimed at implementing advanced features while also focusing on '''fault tolerance''', '''repair''' and '''easy administration'''. [[Btrfs]] not only is a filesystem, but also is partly a volume manager, software-raid, backup-tool, and it is flash-friendly.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Because [[Btrfs]] is different, some things seem unfamiliar and strange. Then [[Btrfs]] is a good starting point to search for answers.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Development of Btrfs started in 2007. Since that time, Btrfs is a part of the Linux kernel and is under active development. The Btrfs code base is '''[https://btrfs.wiki.kernel.org/index.php/Status stable] .''' However, new features are still under development. Its main features and benefits are:
* '''Snapshots''' which do not make a full copy of files
* '''RAID''' - support for software-based RAID 0, RAID 1, RAID 10
* '''Self-healing''' - checksums for data and metadata, automatic detection of silent data corruptions
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
see [[Btrfs]], [https://btrfs.wiki.kernel.org/index.php/Main_Page Btrfs@kernel.org], [https://wiki.archlinux.org/title/Btrfs Btrfs@ARCH-wiki], [https://de.wikipedia.org/wiki/Btrfs Btrfs@wikipedia]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
====Install====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=pamac install btrfs-progs}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== ReiserFS → reiser4 ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
ReiserFS was the first journaling filesystem to be included in the standard kernel. It was actively used by some distros some time ago, but is not currently widely used. Reiser4 is the successor to ReiserFS(3). However, Reiser4 seems not to be integrated in the kernel yet.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
see [https://wiki.archlinux.org/title/Reiser4 Reiser4@ARCH-wiki], [https://en.wikipedia.org/wiki/ReiserFS ReiserFS@wikipedia], [https://en.wikipedia.org/wiki/Reiser4 Reiser4@wikipedia], [https://reiser4.wiki.kernel.org/ Reiser4@kernel.org]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
====Install====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=pamac install reiserfsprogs reiser4progs}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Windows ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
filesystems mostly used in windows
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== NTFS ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It is the most widely used filesystem on windows these days. It does exist in different versions, but unlike FAT32, all of them offer the following points:
* Large files> 4GB
* Long file names with UTF16 up to 255 characters
* Rights management, ACL
* Journaling of metadata
* Compression, encryption, ...
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Currently there are some restrictions when using NTFS with Linux. If windows is suddenly switched off or goes into hibernating, the NTFS filesystem is left in a "dirty-state". When Windows starts again, NTFS is the first to be cleaned. This operation is currently not supported by the Linux driver. Then Linux shows the NTFS filesystem as read-only to be on the safe side.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
see [https://wiki.archlinux.org/title/NTFS NTFS@ARCH-wiki], [https://en.wikipedia.org/wiki/NTFS NTFS@wikipedia]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{warning |If you regularly switch between Windows and Linux, you should switch off "hibernation", "Hybrid Boot", "Fast Boot" in Windows. Then Linux has always full (read / write) access to NTFS drives.
* [https://forum.manjaro.org/t/all-of-my-files-are-in-read-only-mode/83777/7 all-of-my-files-are-in-read-only-mode@forum]
}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
====Install====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=pamac install ntfs-3g}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== DOS ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
filesystems under DOS and early windows on a lot of floppydisks and USB-sticks
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== FAT16 → FAT32 (+VFAT) ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a traditional filesystem under DOS and early Windows versions. Even today it can be found on many floppy disks, USB sticks and hard drives. It is supported by all types of operating systems and is therefore often used to exchange files, to pass them on, or to keep them accessible to both operating systems in the case of dualboot.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Even with FAT32, this comes not without its disadvantages.
* no support for user rights or xattr
* severely restricted file names (8.3 or LFN for VFAT, no distinction between lowercase and uppercase)
* no files over 2GB (FAT16) 4GB (FAT32)
* no journaling
* not robust
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{warning | FAT Filesystems do not use journaling. Data on such filesystems is vulnerable to irreparable corruption due to ''improper ejection or power outage''.}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
see [https://wiki.archlinux.org/title/FAT FAT@ARCH-wiki], [https://en.wikipedia.org/wiki/File_Allocation_Table FAT@wikipedia]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
====Install====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=pamac install dosfstools}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== exFAT ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Microsoft developed the exFAT (Extended File Allocation Table) in 2006 and optimized it for flash memories such as USB sticks and SD cards. It can store large files and large numbers of files, and it can manage very large partitions. It is supported by Linux, Windows, macOS and many other devices and is one of the most compatible filesystems. ExFAT is included in Linux 5.4 and higher.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Flash friendly
* No support for user rights or xattr
* Files over 4 GB
* Checksums for metadata
* No journal
* Not robust
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{warning | exFAT FS does not use journaling. Data on such a filesystem is vulnerable to irreparable corruption due to ''improper ejection or power outage''.}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
see [https://en.wikipedia.org/wiki/ExFAT ExFAT@wikipedia]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
====Install====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=pamac install exfatprogs}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== macOS ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Filesystems mostly used in macOS
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== HFS → HFS+ ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
see [https://en.wikipedia.org/wiki/HFS_Plus HFSPlus@wikipedia]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
====Install from AUR====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
{{UserCmd|command=pamac install hfsprogs}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Others ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== XFS ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
see [https://wiki.archlinux.org/title/XFS XFS@ARCH-wiki]
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===ZFS===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
see [https://wiki.archlinux.org/title/ZFS ZFS@ARCH-wiki]
</div>

==Comparaisons==
{| class="wikitable sortable"
|+Utilisation possible des systèmes de fichiers
|-
!Filesystem!!Manjaro!!Win10!!OSX!!Win9x, DOS
|-
|ext2||●||▷ ExtFS||●||
|-
|ext3/4||●||▷ ExtFS||?||
|-
|btrfs||● btrfs-progs||▷ ExtFS, WinBtrfs||-||-
|-
|reiser3||● reiser4progs||▷ RFSTool||?||-
|-
|reiser4||○ reiserfs||?||?||-
|-
|NTFS||○ ntfs-3g<br>▶ 5.15?? ntfs3||●||?||
|-
|FAT32||● dosfstools||●||●||●
|-
|exFAT||▶ 5.4 exfatprogs||●||?||?
|-
|HFS||○ hfsprogs (AUR)||?||●||
|-
|XFS||?||▷ ExtFS||?||
|-
|ZFS||?||?||?||
|}

  ● = entièrement pris en charge, outils supplémentaires à installer
 ▶ = inclus depuis le noyau x.x.x 
 ○ = partiellement pris en charge
 ▷ = possible via des outils externes
 ? = n'hésitez pas à l'étendre ;-)

<div lang="en" dir="ltr" class="mw-content-ltr">
{| class="wikitable sortable"
|+ Some important properties
|-
! Properties !!ext2!!ext3!!ext4!!btrfs||reiserfs(3)||XFS
|-
|journaling ||-||● ordered||● ordered||● full||▶ 2.6||●
|-
|barriers ||-||||●||●
|-
|checksum ||-||-||◎ metadata||● full||●
|-
|kompression||-||-||-||●,<br><small>zstd ▶ 4.14/5.1</small>||
|-
|encryption||-||-||▶ 4.13||-
|-
|snapshots||-||-||-||●||-
|-
|TRIM possible||-||-||▶ 2.6.33||▶ 4.3
|-
|xattr, ACL||◎||?||ACL||ACL||ACL
|-
|small repair||● fsck||● fsck||● fsck||● auto||reiserfsck
|-
|journal repair||● fsck||● fsck||● fsck||● auto 3.2||
|-
|repair after power loss||-||?||● tune2fs, fsck||● auto, scrub||
|-
|since||1993||2001||2008||2009||2001
|}
</div>

=Voir également=

<div lang="en" dir="ltr" class="mw-content-ltr">
[https://en.wikipedia.org/wiki/ExFAT Wikipedia:exFAT]<br />
[https://en.wikipedia.org/wiki/Comparison_of_file_systems Wikipedia:Comparison of filesystems]<br />
[https://wiki.archlinux.org/index.php/Filesystems Archwiki:filesystems]<br />
</div> 
[[Category:Contents Page{{#translation:}}]]
[[Category:filesystems{{#translation:}}]]