So another issue that you might encounter are file system issues.
A real corruption does occur, but it doesn't often happen.
And when it happens for modern file systems,
it's normally automatically fixed if it's fixable.
And if it's not fixable, there's one solution, backup tape.
You won't have to do that on the exam.
What you might have to do on the exam
is to fix a problem that occurs because of making
typos in ETC FS step.
Now, what you need to do in order to fix, if necessary,
you remount the file system in read-write mode,
and you edit ETC FS step.
Apart from that, fragmentation can be an issue,
and different tools exist to fix.
That's also unlikely to be seen on the exam.
But the tools are XFS underscore FSR,
which is a file system reorganizer,
or E4 Defrag, which can be used to defragment EXT4.
Now, most important for your exam
are the FS step-related issues.
So they can occur after modifying ETC FS step
because you forgot something or you make a silly typo.
To prevent having issues, it's a smart idea
to verify that your FS step is valid.
You can use mount minus A to mount all file systems
in ETC FS step that haven't been mounted yet.
And if there's an issue, that will show at that moment.
Otherwise, you can find mount minus minus
verify to verify the syntax.
And to really verify that all works well,
use reboot after making changes to ETC FS step.
That's really something that I advise.
Once you are done with all your storage and FS step-related
work, reboot your system.
Because if you get in trouble, then you still
have sharp in your mind what you've just been doing.
And hopefully, you'll be able to fix it.
Now, let me create an issue in ETC FS step
and show you how to fix it.
So let's try to break the ETC FS step.
I'm using dev SEA1.
That's a non-existing device.
That is right.
Mounting it on MNT and using EXT4
and other non-existing options, defaults, and 0 and 0.
And then I'm going to reboot.
So if you have a problem in ETC FS step,
then the risk is that you can't reboot anymore.
And you will drop an emergency shell.
So what are you going to do in the emergency shell?
Well, you enter the root password.
You verify that you can write to your file system.
And if that is not the case, mount minus o remount comma
rw on slash.
And then you edit your ETC FS step.
And you are trying to find the problem.
And here is the problem.
Well, I'm deleting my problem.
And now I'm done.
And then you can quit the emergency shell
using Control D. And that will normally
resume the boot procedure.
And hopefully, it will get you back
in normal operational state.
You will notice that even in the case
that there is errors in ETC FS step,
RHEL 10 is capable of continuing to boot anyway.
It's a pretty solid operating system.
And you won't get in deep trouble very fast.