translator
1,032
edits
m (Link zu Btrfs hinzugefügt) |
(Btrfs out of space) |
||
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
<languages/> | <languages/> | ||
__TOC__ | __TOC__ | ||
<translate> | <translate> | ||
Line 43: | Line 43: | ||
<!--T:41--> | <!--T:41--> | ||
Because [[Btrfs]] is different, some things seem unfamiliar and strange. Then [[Btrfs]] is a good starting point to search for answers. | Because [[Btrfs]] is different, some things seem unfamiliar and strange. Then the page [[Btrfs]] is a good starting point to search for answers. | ||
<!--T:42--> | <!--T:42--> | ||
Line 53: | Line 53: | ||
<!--T:43--> | <!--T:43--> | ||
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] | 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] | ||
{{BoxWarning|Maintenance|When using snapshots, you must be particularly careful not to use up all the space on the file system -> [[Btrfs#Out_of_space]]}} | |||
====Install==== <!--T:21--> | ====Install==== <!--T:21--> | ||
Line 62: | Line 64: | ||
<!--T:45--> | <!--T:45--> | ||
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. | 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. | ||
{{BoxWarning|As of kernel 6.13|reiserFS will no longer be supported.}} | |||
<!--T:46--> | <!--T:46--> | ||
Line 88: | Line 92: | ||
<!--T:51--> | <!--T:51--> | ||
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. | 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. The same thing may happen, when NTFS becomes damaged. | ||
<!--T:53--> | <!--T:53--> | ||
Line 94: | Line 98: | ||
<!--T:52--> | <!--T:52--> | ||
{{ | {{BoxWarning|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] | * [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] | ||
}} | |||
{{BoxDanger|If your NTFS file system becomes corrupted|It is strongly recommended that you only repair the file system using the original Windows tools. Anything else is highly risky. | |||
}} | }} | ||