1 00:00:00,000 --> 00:00:14,240 Hey guys and welcome back. 2 00:00:14,240 --> 00:00:18,400 So in this skill right here we have a lot of really cool things to cover. 3 00:00:18,400 --> 00:00:22,199 What we're going to be looking at are some of the tools that we're going to be using 4 00:00:22,199 --> 00:00:26,920 to configure and repair EXT based file systems. 5 00:00:26,920 --> 00:00:31,960 Now as you recall we did mention that we have these different types of file systems. 6 00:00:31,960 --> 00:00:40,000 We can have EXT2 which is really rarely used nowadays except for sometimes USB drives may 7 00:00:40,000 --> 00:00:49,359 still utilize EXT2 but that was since replaced with EXT3 and then later by EXT4. 8 00:00:49,359 --> 00:00:55,600 Now this family of file system the EXT family is obviously very widely used so it is important 9 00:00:55,600 --> 00:01:01,600 for us to be able to understand the tools that we can use to like I say configure and 10 00:01:01,600 --> 00:01:04,120 repair these file systems. 11 00:01:04,120 --> 00:01:09,120 Now we did also mention very briefly in the last skill that we have other file systems 12 00:01:09,120 --> 00:01:10,120 too. 13 00:01:10,120 --> 00:01:14,400 Now one of those file systems was XFS. 14 00:01:14,400 --> 00:01:22,359 Now XFS was designed for high performance and it was used as an alternative to the EXT 15 00:01:22,359 --> 00:01:23,480 style file system. 16 00:01:23,480 --> 00:01:30,560 So likewise it does make sense therefore that we do have different tools to manage and repair 17 00:01:30,560 --> 00:01:36,120 XFS based file systems so we certainly will want to be looking at that and those tools 18 00:01:36,120 --> 00:01:37,960 within this skill as well. 19 00:01:37,960 --> 00:01:43,280 Now some other things we're going to have to discuss are looking at removable media. 20 00:01:43,280 --> 00:01:48,240 This would be things such as CD ROMs and USBs that type of thing. 21 00:01:48,240 --> 00:01:52,120 And then we're also going to mention something relating to SMART. 22 00:01:52,120 --> 00:01:57,760 Now this is not to be confused with your smartphone or your smartwatch. 23 00:01:57,760 --> 00:02:02,400 Smart in this context is a little bit different but certainly within this skill we're going 24 00:02:02,400 --> 00:02:04,640 to be looking at that too. 25 00:02:04,640 --> 00:02:11,280 And then we will be having a look at something called AutoFS a super cool and efficient tool 26 00:02:11,280 --> 00:02:14,879 that you can use with respect to mounting your file systems. 27 00:02:14,879 --> 00:02:18,960 So what we are learning within this skill is going to be building upon what we've learned 28 00:02:18,960 --> 00:02:24,920 in the previous skill, taking that information and going a little deeper and a little broader. 29 00:02:24,920 --> 00:02:32,120 So let's first begin by talking about the EXT file system then that's where we'll start 30 00:02:32,120 --> 00:02:33,120 from. 31 00:02:33,120 --> 00:02:34,120 So let's begin then. 32 00:02:34,120 --> 00:02:39,719 Now if you do not recall from the previous skill what I happened to do is I went and 33 00:02:39,719 --> 00:02:43,080 added a new disk to my virtual machine. 34 00:02:43,080 --> 00:02:48,920 That means when I run my LSBLK-F option we can see I also have this new disk. 35 00:02:48,919 --> 00:02:52,319 Disk, disk B here you see that, SDB. 36 00:02:52,319 --> 00:02:55,679 And what I did was I created a partition, in this case partition 1. 37 00:02:55,679 --> 00:03:00,839 I made it a primary partition and then I formatted it with a file system. 38 00:03:00,839 --> 00:03:05,639 This time an EXT4 file system, so an EXT based file system indeed. 39 00:03:05,639 --> 00:03:10,279 Now right now you may recall that this partition right here is not mounted. 40 00:03:10,279 --> 00:03:12,079 We do not have a mount point. 41 00:03:12,079 --> 00:03:17,639 So depending on if you happen to be following along from the previous skill directly and 42 00:03:17,639 --> 00:03:22,439 you have also followed this procedure whereby you have another disk, you have a new partition. 43 00:03:22,439 --> 00:03:27,679 If you happen to have that partition mounted, i.e. in your output you have a mount point 44 00:03:27,679 --> 00:03:32,639 here, then what you would want to do would be to unmount that particular partition. 45 00:03:32,639 --> 00:03:35,679 In my case as you can see here it is not mounted. 46 00:03:35,679 --> 00:03:39,239 Again I could check this with my mount command and get it for SDB. 47 00:03:39,239 --> 00:03:42,560 Notice we do not have any output the way we do for SDA. 48 00:03:42,560 --> 00:03:44,279 So mine is definitely unmounted. 49 00:03:44,280 --> 00:03:50,400 Now with that said, what I want to do is to run a command we saw within the previous skill. 50 00:03:50,400 --> 00:03:56,439 That is the FSCK command, otherwise colloquially known as the FISC command. 51 00:03:56,439 --> 00:04:01,520 If you do not recall what the FSCK command does, or FISC if you prefer, this is going 52 00:04:01,520 --> 00:04:05,520 to allow you to check and repair a Linux file system. 53 00:04:05,520 --> 00:04:08,960 So I will use the FISC command with my super user privileges. 54 00:04:08,960 --> 00:04:15,280 I will say dash Y to answer yes to any prompts, i.e. if FISC finds a problem I want FISC to 55 00:04:15,280 --> 00:04:18,560 go ahead and address and repair that issue. 56 00:04:18,560 --> 00:04:21,519 And I will target the partition on my second disk right here. 57 00:04:21,519 --> 00:04:22,920 So I will do this right here. 58 00:04:22,920 --> 00:04:27,360 We can see here that this is clean, we have no issues at all. 59 00:04:27,360 --> 00:04:33,720 Now we know that this partition happens to be an EXT based file system. 60 00:04:33,720 --> 00:04:38,879 We saw this from the output of our LSBLK EXT4. 61 00:04:38,879 --> 00:04:43,839 Now one thing I want you to notice is what the FISC command is actually doing here. 62 00:04:43,839 --> 00:04:49,319 To check this out, what I want to do is I want to locate where the FISC command is actually 63 00:04:49,319 --> 00:04:50,600 coming from. 64 00:04:50,600 --> 00:04:57,920 So what I will see here is which FSCK and we can see this is actually located at user 65 00:04:57,920 --> 00:04:59,639 Sbin FISC. 66 00:04:59,639 --> 00:05:05,920 So what I want to do here is I actually want to list everything within the Sbin directory 67 00:05:05,920 --> 00:05:08,120 here with respect to FISC. 68 00:05:08,120 --> 00:05:11,560 So what I can say is list my Sbin directory. 69 00:05:11,560 --> 00:05:16,560 Now if I enter, this is going to give me a ton of information far too much. 70 00:05:16,560 --> 00:05:20,480 So what I will do is I will grep for FISCK. 71 00:05:20,480 --> 00:05:24,639 Now what I want you to see here are all these different types of options. 72 00:05:24,639 --> 00:05:32,360 We have FISCK EXT2 for example or EXT4 or FAT for file allocation table. 73 00:05:32,360 --> 00:05:34,480 All of these different file systems. 74 00:05:34,480 --> 00:05:39,680 Now here is what is actually happening when we run this FISC command. 75 00:05:39,680 --> 00:05:43,200 And this is not just some random trivia I'm telling you, this is something you really 76 00:05:43,200 --> 00:05:46,439 want to be remembering for the purposes of the examination. 77 00:05:46,439 --> 00:05:51,040 This command here FISC is ultimately acting as a front end. 78 00:05:51,040 --> 00:05:56,200 Because when we actually invoke this command, what is going to happen is under the hood, 79 00:05:56,200 --> 00:06:01,319 FISC is ultimately going to query what type of file system it is running against. 80 00:06:01,319 --> 00:06:08,159 So when I say FISC against dev, SDB1, what FISC is actually doing, it's querying and 81 00:06:08,159 --> 00:06:12,879 saying hey, what type of file system is this and it looks it up and it gets the information 82 00:06:12,879 --> 00:06:16,800 back that this is an EXT4 file system. 83 00:06:16,800 --> 00:06:23,039 And then because it has assessed this information, it's actually going to call one of these commands 84 00:06:23,039 --> 00:06:24,039 particularly. 85 00:06:24,039 --> 00:06:30,240 So if it finds it is an EXT4 file system, it will actually use this little program right 86 00:06:30,240 --> 00:06:31,240 here. 87 00:06:31,240 --> 00:06:34,480 And what we're getting here is a high degree of abstraction. 88 00:06:34,480 --> 00:06:39,319 Now this is very, very useful because us as the user, we don't have to concern ourselves 89 00:06:39,319 --> 00:06:41,840 with what type of file system we are using. 90 00:06:41,840 --> 00:06:46,519 We can just run the FISC command, let the tool figure out these specifics and everything 91 00:06:46,519 --> 00:06:48,519 works almost automatically. 92 00:06:48,519 --> 00:06:54,960 Okay, but understand here that these different options are all the different types of file 93 00:06:54,960 --> 00:06:58,480 systems that can ultimately be repaired by FISC. 94 00:06:58,480 --> 00:07:05,120 But if I try to manually invoke one of these programs against the wrong file system type, 95 00:07:05,120 --> 00:07:06,120 what's what will happen? 96 00:07:06,120 --> 00:07:09,080 So I can grab MSDOS for example right here. 97 00:07:09,080 --> 00:07:17,560 So I'll say it's sudo FISC.MSDOS and then I will target my EXT4 based file system, 98 00:07:17,560 --> 00:07:18,560 so SDB1. 99 00:07:18,560 --> 00:07:24,319 And if I hit enter, it's saying the logical sector size is zero. 100 00:07:24,319 --> 00:07:29,800 So this particular program is looking for a formatting style which does not exist on 101 00:07:29,800 --> 00:07:30,800 EXT4. 102 00:07:30,800 --> 00:07:35,319 So it just simply is not going to be able to inspect nor repair this file system. 103 00:07:35,319 --> 00:07:39,879 But I can if I so choose explicitly call that particular program. 104 00:07:39,879 --> 00:07:46,360 So I can actually say EXT4, which would be the correct file system and to enter and we 105 00:07:46,360 --> 00:07:47,639 get the same effect. 106 00:07:47,639 --> 00:07:51,240 But really just to remember, we do not have to do such a thing. 107 00:07:51,240 --> 00:07:55,400 We can just call FISC and FISC will automatically figure this out. 108 00:07:55,400 --> 00:07:57,680 Really important concept to be remembering. 109 00:07:57,680 --> 00:08:03,680 So I can say sudo FISC against devsda5 which is mounted. 110 00:08:03,680 --> 00:08:07,240 Notice here it's saying this is mounted cannot continue aborting. 111 00:08:07,240 --> 00:08:12,639 But this begs the question, we have this root file system mounted right here, which is utilizing 112 00:08:12,639 --> 00:08:15,319 this disk with this particular file system. 113 00:08:15,319 --> 00:08:21,680 How in earth would we be able to scan this then and be able to leverage the ability of 114 00:08:21,680 --> 00:08:28,879 FISC to repair this EXT4 based file system if there was indeed a problem to solve. 115 00:08:28,879 --> 00:08:31,319 So this is a little bit of a problem. 116 00:08:31,319 --> 00:08:36,840 Our system ultimately requires that the root file system be mounted and we can't scan this 117 00:08:36,840 --> 00:08:40,519 particular file system because it is mounted. 118 00:08:40,519 --> 00:08:44,879 Well the answer actually lies in something we talked about in the previous skill and 119 00:08:44,919 --> 00:08:48,360 that is in the SAFS tab file. 120 00:08:48,360 --> 00:08:50,840 So let me just quickly show you that one once again. 121 00:08:50,840 --> 00:08:57,039 So go into, in fact let me just say nano with super user privileges and also FSTAB and to 122 00:08:57,039 --> 00:08:58,039 enter. 123 00:08:58,039 --> 00:09:00,519 Now you may recall we talked about these different columns here. 124 00:09:00,519 --> 00:09:06,320 We have the file system, the mount points, the type, the options, then the dump value 125 00:09:06,320 --> 00:09:08,120 and then the pass value. 126 00:09:08,120 --> 00:09:13,440 Now I kind of skipped over dump and pass but I definitely don't want to skip over pass 127 00:09:13,480 --> 00:09:15,440 in this portion right here. 128 00:09:15,440 --> 00:09:20,880 So what pass is ultimately going to do is going to allow us to invoke FISC. 129 00:09:20,880 --> 00:09:26,760 So really this value here on the right hand side, this is the priority value. 130 00:09:26,760 --> 00:09:34,640 So this value here will mean that indeed the root file system will be scanned by FISC. 131 00:09:34,640 --> 00:09:40,280 The thing is it will be scanned upon a reboot before it actually has been mounted when it 132 00:09:40,319 --> 00:09:41,600 is going to mount it. 133 00:09:41,600 --> 00:09:44,319 So to speak it will run this FISC command. 134 00:09:44,319 --> 00:09:49,199 Now one thing to note here is that this does not mean, and I mentioned this in the previous 135 00:09:49,199 --> 00:09:55,199 skill, this absolutely does not mean that every time the file system is booted the root 136 00:09:55,199 --> 00:09:57,240 file system is going to be scanned. 137 00:09:57,240 --> 00:09:58,240 Nope. 138 00:09:58,240 --> 00:10:05,000 The number here is simply the priority and if it does have a number that is not zero 139 00:10:05,000 --> 00:10:07,439 then it is going to be scanned by FISC. 140 00:10:07,440 --> 00:10:13,560 However if I happen to change this value and I change it to be zero this would mean that 141 00:10:13,560 --> 00:10:18,520 the root file system would never ever ever be scanned by FISC upon reboot. 142 00:10:18,520 --> 00:10:22,960 But for now I will leave it at one because I do want it to be checked by FISC. 143 00:10:22,960 --> 00:10:28,160 Now this actually begs the question if this number does not denote how frequent the check 144 00:10:28,160 --> 00:10:33,480 is going to happen how do we actually make such a decision, how do we actually control 145 00:10:33,480 --> 00:10:37,040 how often FISC is going to check that root file system? 146 00:10:37,039 --> 00:10:43,079 Well the answer lies in the command called tune to FS and this is another tool that we 147 00:10:43,079 --> 00:10:46,360 can use with respect to our EXT based file systems. 148 00:10:46,360 --> 00:10:48,399 So let me show you how this works. 149 00:10:48,399 --> 00:10:54,039 So let's have a look at tune to FS then and see how this can help us with respect to our 150 00:10:54,039 --> 00:10:55,919 EXT based file systems. 151 00:10:55,919 --> 00:11:02,360 I will say man tune to FS and we can see here this is going to allow us to adjust file system 152 00:11:02,360 --> 00:11:07,639 parameters on EXT 2, 3 and 4 based file systems. 153 00:11:07,639 --> 00:11:12,919 So notice this is a tool for the EXT family of file systems. 154 00:11:12,919 --> 00:11:16,360 You're not going to be able to use this on something like say XFS. 155 00:11:16,360 --> 00:11:21,399 So what I'm going to do here is I'm going to list my current settings. 156 00:11:21,399 --> 00:11:27,960 What I shall do is I will say tune to FS-L and I am forgetting a very important point. 157 00:11:27,960 --> 00:11:34,080 I actually have to give as an argument the file system whose settings I want to list. 158 00:11:34,080 --> 00:11:41,639 So in this case here I will just use devsdb1 and if I hit enter I am forgetting super 159 00:11:41,639 --> 00:11:42,639 user privileges. 160 00:11:42,639 --> 00:11:45,800 Clearly I am still asleep so we'll try again. 161 00:11:45,800 --> 00:11:47,360 Type in my password of course. 162 00:11:47,360 --> 00:11:50,280 Hit enter and there we go a little bit better. 163 00:11:50,280 --> 00:11:55,200 Okay so if we scroll on up to the top here we can see a whole bunch of information. 164 00:11:55,200 --> 00:12:00,560 You can see things such as the volume name for this particular file system as of right 165 00:12:00,560 --> 00:12:03,160 now there is no volume name set. 166 00:12:03,160 --> 00:12:09,480 So if I wanted to tune these settings say for example the file system name I could actually 167 00:12:09,480 --> 00:12:12,640 do this directly via tune to FS. 168 00:12:12,640 --> 00:12:16,920 The way I can do this is by using the dash capital L flag. 169 00:12:16,920 --> 00:12:24,320 I can say sudo tune to FS dash capital L and then I'll give the name of the label that 170 00:12:24,720 --> 00:12:30,320 assign to this particular file system so I'll just call it my label because as we know I 171 00:12:30,320 --> 00:12:36,040 am completely devoid of all creativity so keep this simple and then I'll specify what 172 00:12:36,040 --> 00:12:37,200 it is I want to target. 173 00:12:37,200 --> 00:12:43,760 I want to target sdb1 so if I hit enter now that will now be tuned if I arrow up and list 174 00:12:43,760 --> 00:12:44,760 my new settings. 175 00:12:44,760 --> 00:12:47,480 If I scroll on up a little bit here we go. 176 00:12:47,480 --> 00:12:52,880 At the very top now the settings have been tuned such that the volume name is now my 177 00:12:52,880 --> 00:12:53,880 label. 178 00:12:53,919 --> 00:12:59,600 Now with respect to what we can see here with the tune to FS outputs we have a lot of settings 179 00:12:59,600 --> 00:13:03,799 and that means we can change and tune a lot of these settings. 180 00:13:03,799 --> 00:13:08,679 One setting which is very important to what we just talked about with respect to Fisk 181 00:13:08,679 --> 00:13:10,879 is going to be our interval value. 182 00:13:10,879 --> 00:13:13,519 Let me show you what that is if I scroll on down. 183 00:13:13,519 --> 00:13:18,559 We can see here that the check interval is the value none. 184 00:13:18,559 --> 00:13:23,720 So what I'm going to do is I'm going to actually first change this value and then I'll explain 185 00:13:24,160 --> 00:13:25,600 what we've actually done. 186 00:13:25,600 --> 00:13:31,000 So the way I can actually change this interval is by using the dash I flag. 187 00:13:31,000 --> 00:13:38,759 Okay think of I for interval so I'll say sudo tune to FS dash I and I'll give it a particular 188 00:13:38,759 --> 00:13:39,759 value. 189 00:13:39,759 --> 00:13:45,720 Now if I happen to say the value 7 this is going to correspond to 7 days and then I'll 190 00:13:45,720 --> 00:13:50,399 give the actual targets file system which will be sdb1. 191 00:13:50,480 --> 00:13:58,360 If I hit enter that will now be changed and notice here it says 604800 seconds. 192 00:13:58,360 --> 00:14:04,559 What this actually means is that I've given the value 7 days it's translated it into seconds 193 00:14:04,559 --> 00:14:09,399 this is how many seconds that is and if I list everything once again we scroll on up. 194 00:14:09,399 --> 00:14:14,799 We can see the check interval is now at one week but what exactly are we talking about 195 00:14:14,799 --> 00:14:17,679 with respect to this check interval. 196 00:14:17,679 --> 00:14:22,679 Well this is exactly what we talked about when we were speaking about the pass option 197 00:14:22,679 --> 00:14:24,239 within FS tab. 198 00:14:24,239 --> 00:14:30,639 So open this FS tab here we have the priority value one just meaning that FISC is going 199 00:14:30,639 --> 00:14:33,399 to be run against this file system. 200 00:14:33,399 --> 00:14:38,559 Now remember I said this didn't actually dictate when or how often this would happen. 201 00:14:38,559 --> 00:14:42,319 We would do it another way this is what we're doing right now. 202 00:14:42,400 --> 00:14:49,120 What we're saying here is that after one week we want to be running the FISC utility against 203 00:14:49,120 --> 00:14:50,960 this particular file system. 204 00:14:50,960 --> 00:14:58,080 Now right now this will actually not take effect FISC will not check sdb1 because sdb1 is not 205 00:14:58,080 --> 00:15:00,720 defined within FISC. 206 00:15:00,720 --> 00:15:07,000 So what I could do here is I could add a particular option I could say dev sdb1 and let me just 207 00:15:07,000 --> 00:15:11,560 mount this in my documents folder say for example it's ext4. 208 00:15:11,599 --> 00:15:17,399 I'll give it the defaults and I'll say zero and I'll put the pass value to the priority 209 00:15:17,399 --> 00:15:21,959 two and just before I save this what I should actually do is give the fill path so that 210 00:15:21,959 --> 00:15:28,599 should be home ipv0 documents so I'll save here and exit and I will now run the mount-a 211 00:15:28,599 --> 00:15:31,279 command which will invoke FS tab. 212 00:15:31,279 --> 00:15:39,039 So now if I say lsblk-f this file system is now mounted here and because it is now an 213 00:15:39,039 --> 00:15:42,399 FS tab it will survive multiple reboots. 214 00:15:42,399 --> 00:15:47,959 So just like the problem we had with our root directory how could we run FISC against this 215 00:15:47,959 --> 00:15:52,639 because now it's going to be mounted every time we have the computer turned on but like 216 00:15:52,639 --> 00:16:00,039 we saw with our tune2fs now configured after a week has elapsed the next reboot that happens 217 00:16:00,039 --> 00:16:07,599 tune2fs will run against sdb1 before it actually is mounted when the system is beginning to 218 00:16:07,599 --> 00:16:08,599 boot up. 219 00:16:08,680 --> 00:16:13,600 Another important point to note here is that we have a maximum mount count of minus one 220 00:16:13,600 --> 00:16:19,720 what this means is that the maximum mount count is not in effect now just like with 221 00:16:19,720 --> 00:16:25,120 the other options tune2fs is going to allow us to modify this particular value I can do 222 00:16:25,120 --> 00:16:30,759 so with the dash c flag and now I can specify the maximum mount count so in this case I 223 00:16:30,759 --> 00:16:36,680 will change it to five and then specify the disk I want to target so sdb1 and then target 224 00:16:36,679 --> 00:16:43,120 the particular partition sdb1 if I hit enter we have now changed the maximum mount count 225 00:16:43,120 --> 00:16:49,879 to five I can then list everything once again instead we no longer have negative one we 226 00:16:49,879 --> 00:16:55,279 have the mount count of five and right now the mount count is one so check this out if 227 00:16:55,279 --> 00:17:02,079 I happen to unmount stave sdb1 again with the sudo command and then I mount it once 228 00:17:02,080 --> 00:17:07,440 again watch what happens if I list my options one more time notice here the mount count 229 00:17:07,440 --> 00:17:14,160 has incremented to the value two and again if I unmounted and mounted and listed again 230 00:17:14,160 --> 00:17:19,240 the mount count increments once again now what we have done here is we have set a maximum 231 00:17:19,240 --> 00:17:25,600 value of five and then once we go beyond five what is going to happen is fisk again is going 232 00:17:25,600 --> 00:17:32,059 to be invoked meaning that once we have breached that limit of five the next boot that particular 233 00:17:32,179 --> 00:17:39,539 file system and sdb1 is going to be checked by fisk again because we have that pass value 234 00:17:39,539 --> 00:17:45,419 configured within it's a fs tab hopefully these pieces are beginning to come together 235 00:17:45,419 --> 00:17:49,500 so you can see how everything relates to one another now the thing is you might be wondering 236 00:17:49,500 --> 00:17:54,899 is that we may have a potential contradiction we have fisk being invoked after one week 237 00:17:54,899 --> 00:18:00,500 apparently as well as after five reboots so when is it going to take effect after a week 238 00:18:00,500 --> 00:18:07,019 or after five reboots the reality is both are still in play and the answer is whatever 239 00:18:07,019 --> 00:18:15,539 one comes first meaning that even if I have no more reboots or no more mounts and unmounts 240 00:18:15,539 --> 00:18:21,099 should I say more accurately then even if we don't breach this five value once the week 241 00:18:21,099 --> 00:18:27,980 has elapsed the next reboots fisk is going to be invoked now conversely if I happen to 242 00:18:28,099 --> 00:18:34,579 breach this value before the week has elapsed say for example I unmounts and mount a few 243 00:18:34,579 --> 00:18:40,420 more times within this very day even though a week has not elapsed fisk will still be 244 00:18:40,420 --> 00:18:46,900 invoked and in fact if I just unmounts, mounts, unmounts and mounts and one more time so I 245 00:18:46,900 --> 00:18:52,980 have breached this value I list my values notice the mount count has actually exceeded 246 00:18:52,980 --> 00:18:58,299 the maximum count but fisk has not yet run because like I say the system is still up 247 00:18:58,299 --> 00:19:04,259 the disks are still mounted but what's going to happen is that upon the next reboots whenever 248 00:19:04,259 --> 00:19:09,900 this particular file system SDB1 is going to be mounted before that actually happens 249 00:19:09,900 --> 00:19:16,099 fisk is going to run so indeed if I happen to just say reboot and reboot the system as 250 00:19:16,099 --> 00:19:21,579 my machine begins to load up before the process is complete fisk is going to be ran against 251 00:19:21,699 --> 00:19:26,779 SDB1 we can actually see file system checks in progress at the bottom of the screen here 252 00:19:26,779 --> 00:19:33,259 this is fisk actually operating against SDB1 because we did breach that maximum mount count 253 00:19:33,259 --> 00:19:41,179 and now I am back in the system we do an LSBLK-F SDB1 has been mounted but in the meantime 254 00:19:41,179 --> 00:19:47,980 during the boot this file system was checked by fisk for any potential errors as we can see here 255 00:19:47,980 --> 00:19:52,940 the tune to FS command really is very very important to understand how it interacts with 256 00:19:52,940 --> 00:19:58,860 the configurations within the xcfs tab file is very very important indeed now we do have a 257 00:19:58,860 --> 00:20:04,299 couple more tools that we want to be looking at with respect to the ext based file systems now 258 00:20:04,299 --> 00:20:08,380 what are those tools well that's what we're going to be talking about in the very next nuggets I 259 00:20:08,380 --> 00:20:11,579 hope this has been informative for you and I'd like to thank you for viewing