Fsck - Revision history

Jamie at 05:22, 15 December 2022

2022-12-15T05:22:50Z

Jamie at 05:19, 15 December 2022

2022-12-15T05:19:34Z

Jamie at 19:34, 29 July 2021

2021-07-29T19:34:13Z

Jamie at 18:56, 29 July 2021

2021-07-29T18:56:28Z

Jamie at 18:55, 29 July 2021

2021-07-29T18:55:42Z

Jamie at 18:53, 29 July 2021

2021-07-29T18:53:52Z

Jamie at 18:52, 29 July 2021

2021-07-29T18:52:11Z

Jamie at 18:50, 29 July 2021

2021-07-29T18:50:57Z

Jamie at 18:50, 29 July 2021

2021-07-29T18:50:09Z

Jamie at 18:44, 29 July 2021

2021-07-29T18:44:37Z

← Older revision		Revision as of 05:22, 15 December 2022
Line 18:		Line 18:

	CramFS is mostly used on embedded systems & Minix is used on the Minix operating system, and designed to be more UNIX-like.		CramFS is mostly used on embedded systems & Minix is used on the Minix operating system, and designed to be more UNIX-like.
		+
		+	ExFAT is the latest, greatest filesystem that does it all, supporting HUGE file sizes, and is usable by both Windows and Linux!

	Each fsck command has different switches and arguments. To see how to use a particular fsck tool, just type the entire fsck.xxx command by itself and hit the ENTER key, and it should give you the "Usage" page.		Each fsck command has different switches and arguments. To see how to use a particular fsck tool, just type the entire fsck.xxx command by itself and hit the ENTER key, and it should give you the "Usage" page.

@@ Line 4: / Line 4: @@
 <pre style="color:blue">
 [jamie@fc33hw01.dawgland.com:~]$ fsck.
-fsck.btrfs   fsck.ext2    fsck.ext4    fsck.hfs     fsck.msdos   fsck.vfat
+fsck.btrfs   fsck.exfat   fsck.ext3    fsck.fat     fsck.msdos   fsck.vfat
-fsck.cramfs  fsck.ext3    fsck.fat     fsck.minix   fsck.ntfs    fsck.xfs
+fsck.cramfs  fsck.ext2    fsck.ext4    fsck.minix   fsck.ntfs    fsck.xfs
 [jamie@fc33hw01.dawgland.com:~]$ fsck.
 </pre>

← Older revision		Revision as of 19:34, 29 July 2021
Line 141:		Line 141:
	[jamie@fc33hw01.dawgland.com:~]$		[jamie@fc33hw01.dawgland.com:~]$
	</pre>		</pre>
		+
		+
		+	In the case of fsck.ntfs, the fsck tool for NTFS filesystems, there is no help, and typing "fsck.ntfs" without the quotes on a blank line without any switches or arguments produces no output at all! However, upon further examination, we find that "fsck.ntfs" is just a pointer, what in Linux is known as a "Symlink", pointing to another command called "ntfsck". Using the Linux command/tool "which", we can find where this "Symlink" lives on the hard drive. If it were just a regular file, the "which" command also would show it's location:
		+	<pre style="color:blue">
		+	[jamie@fc33hw01.dawgland.com:~]$ which fsck.ntfs
		+	/usr/sbin/fsck.ntfs
		+	[jamie@fc33hw01.dawgland.com:~]$
		+
		+
		+	So, when I do a long file listing, to show all file attributes, you can see the actual symlink and where it points to:
		+	<pre style="color:blue">
		+	[jamie@fc33hw01.dawgland.com:~]$ ls -l /usr/sbin/fsck.ntfs
		+	lrwxrwxrwx. 1 root root 13 Jul 28 2020 /usr/sbin/fsck.ntfs -> ../bin/ntfsck
		+	[jamie@fc33hw01.dawgland.com:~]$
		+	</pre>
		+
		+
		+	So now, if I type ntfsck --help, I get this:
		+	<pre style="color:blue">
		+	[jamie@fc33hw01.dawgland.com:~]$ ntfsck --help
		+	Failed to access '--help': No such file or directory
		+	Error opening partition device: No such file or directory
		+	[jamie@fc33hw01.dawgland.com:~]$
		+
		+
		+	So, I see that I must specify an actual device, which is the partition containing the non-mounted NTFS filesystem. I can't stress enough how important it is to only run all of these tools on partitions that are NOT mounted. This usually means you have to reboot the computer with an alternate device such as a USB flash drive, or other bootable media which contains a "Live operating system" which includes the fsck tools we are referring to.

@@ Line 117: / Line 117: @@
-So, when I then type the command "xfs_repair"(NOTE the under_score!) without the quotes on a blank line without any switches or arguments, I get the following output:
+So, when I then type the command "xfs_repair"(NOTE the required under_score in the command name!) without the quotes on a blank line without any switches or arguments, I get the following output:
 <pre style="color:blue">
 [jamie@fc33hw01.dawgland.com:~]$ xfs_repair

@@ Line 117: / Line 117: @@
-So, when I then type this command:
+So, when I then type the command "xfs_repair"(NOTE the under_score!) without the quotes on a blank line without any switches or arguments, I get the following output:
 <pre style="color:blue">
 [jamie@fc33hw01.dawgland.com:~]$ xfs_repair

@@ Line 106: / Line 106: @@
 [jamie@fc33hw01.dawgland.com:~]$
 </pre>
 My other favorite file system, especially on servers with huge files, is the XFS filesystem, and the fsck.xfs command on a blank line by itself with no switches or arguments produces this:

@@ Line 58: / Line 58: @@
-The above hint indicating to see the 'check' subcommand tell me to type this command to get the usage for fsck.btrfs.  I always try "--help" without the quotes to look for built-in help in most every command-line tool:
+The above hint indicating to see the 'check' subcommand tells me to type this command to get the usage for fsck.btrfs.  I always try "--help" without the quotes to look for built-in help in most every command-line tool:
 <pre style="color:blue">
 [jamie@fc33hw01.dawgland.com:~]$ btrfs check --help

@@ Line 49: / Line 49: @@
-Other fsck tools point you to a different location to get the usage page.  For instance, here is what the fsck.btrfs command on a bland line by itself does:
+Other fsck tools point you to a different location to get the usage page.  For instance, here is what the fsck.btrfs command on a blank line by itself does:
 <pre style="color:blue">
 [jamie@fc33hw01.dawgland.com:~]$ fsck.btrfs

@@ Line 20: / Line 20: @@
 Each fsck command has different switches and arguments.  To see how to use a particular fsck tool, just type the entire fsck.xxx command by itself and hit the ENTER key, and it should give you the "Usage" page.
-For instance, if you want to find out how to use the EXT4 filesystem, just type the command without any arguments or switches:
+For instance, if you want to find out how to use the EXT4 filesystem, just type the command on a blank line without any arguments or switches:
 <pre style="color:blue">
 [jamie@fc33hw01.dawgland.com:~]$ fsck.ext4
@@ Line 58: / Line 58: @@
-Years of experience and the above hint indicating to see the 'check' subcommand tell me to type this command to get the usage for fsck.btrfs:
+The above hint indicating to see the 'check' subcommand tell me to type this command to get the usage for fsck.btrfs.  I always try "--help" without the quotes to look for built-in help in most every command-line tool:
 <pre style="color:blue">
 [jamie@fc33hw01.dawgland.com:~]$ btrfs check --help
@@ Line 104: / Line 104: @@
             -p|--progress               indicate progress
 [jamie@fc33hw01.dawgland.com:~]$
 </pre>

@@ Line 47: / Line 47: @@
 [jamie@fc33hw01.dawgland.com:~]$
 </pre>
-<br /><br />