No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
|description=This test case ensures that disk drive(s) are properly unmounted during a power-down or a restart. | |description=This test case ensures that disk drive(s) are properly unmounted during a power-down or a restart. | ||
|setup= | |setup= | ||
# Install the pre-released version of Fedora to be tested | # Install the pre-released version of Fedora to be tested. | ||
# Reboot the system to the hard drive after the install. | # Reboot the system to the hard drive after the install. | ||
|actions= | |actions= | ||
# On the running system, Switch to a free virtual console using Ctrl+Alt+F<n> shortcut and log in. | # On the running system, Switch to a free virtual console using Ctrl+Alt+F<n> shortcut and log in. | ||
# At the command prompt, issue the following command {{command|journalctl -b /usr/lib/systemd/systemd-fsck}} | # At the command prompt, issue the following command {{command|journalctl -b /usr/lib/systemd/systemd-fsck}} | ||
# Review the journal output. Expected Result 1 below shows an example of a good result. Result 2 below shows an example of a bad result. In the bad result note "Clearing orphaned inode", "Dirty bit is set", and "not properly unmounted". These are example failure indicators. | # Review the journal output. Expected Result 1 below shows an example of a good result. Result 2 below shows an example of a bad result. In the bad result note "Clearing orphaned inode", "Dirty bit is set", and "not properly unmounted". These are example failure indicators. If you see any of these problems in the journalctl output, run the following command {{command|journalctl -b /usr/lib/systemd/systemd-fsck > journal.log}} and attach the resulting file to your bug report. | ||
# Close the Journal output and power off the system using the command {{command|poweroff}}on the virtual console. | # Close the Journal output and power off the system using the command {{command|poweroff}}on the virtual console. | ||
# After a short wait (15 or 20 seconds) power on your test system with the power button. When the system is running, repeat steps 1 through 3 above. | # After a short wait (15 or 20 seconds) power on your test system with the power button. When the system is running, repeat steps 1 through 3 above. | ||
Revision as of 18:31, 2 December 2019
Description
This test case ensures that disk drive(s) are properly unmounted during a power-down or a restart.
Setup
- Install the pre-released version of Fedora to be tested.
- Reboot the system to the hard drive after the install.
How to test
- On the running system, Switch to a free virtual console using Ctrl+Alt+F<n> shortcut and log in.
- At the command prompt, issue the following command
journalctl -b /usr/lib/systemd/systemd-fsck - Review the journal output. Expected Result 1 below shows an example of a good result. Result 2 below shows an example of a bad result. In the bad result note "Clearing orphaned inode", "Dirty bit is set", and "not properly unmounted". These are example failure indicators. If you see any of these problems in the journalctl output, run the following command
journalctl -b /usr/lib/systemd/systemd-fsck > journal.logand attach the resulting file to your bug report. - Close the Journal output and power off the system using the command
poweroffon the virtual console. - After a short wait (15 or 20 seconds) power on your test system with the power button. When the system is running, repeat steps 1 through 3 above.
- Close the Journal output and restart the test system using the command
rebooton the virtual console. - Repeat steps 1 through 3 above.
Expected Results
- Good Result example: -- Logs begin at Mon 2019-08-19 22:09:28 EDT, end at Wed 2019-11-27 19:00:08 EST.
Nov 27 07:28:10 localhost.localdomain systemd-fsck[570]: /dev/mapper/fedora_localhost--live-root: clean, 270336/4587520 files, 3312639/18350080 blocks
Nov 27 07:28:23 localhost.localdomain systemd-fsck[849]: /dev/mapper/fedora_localhost--live-home: clean, 58396/117088256 files, 9028585/468341760 blocks
Nov 27 07:28:23 localhost.localdomain systemd-fsck[848]: /dev/sda1: clean, 416/65536 files, 77941/262144 blocks
2. Bad result example: -- Logs begin at Tue 2019-08-27 09:26:40 CEST, end at Tue 2019-11-26 14:50:14 CET. --
Nov 25 10:25:20 phoenix systemd-fsck[684]: root: recovering journal
Nov 25 10:25:20 phoenix systemd-fsck[684]: root: Clearing orphaned inode 12325283 (uid=1000, gid=1000, mode=0100644, size=641092)
Nov 25 10:25:20 phoenix systemd-fsck[684]: root: Clearing orphaned inode 12331101 (uid=1000, gid=1000, mode=0100644, size=641092)
Nov 25 10:25:20 phoenix systemd-fsck[684]: root: clean, 1023215/26869760 files, 46957728/107451392 blocks
Nov 25 09:25:22 phoenix systemd-fsck[877]: boot: recovering journal
Nov 25 09:25:22 phoenix systemd-fsck[878]: fsck.fat 4.1 (2017-01-24)
Nov 25 09:25:22 phoenix systemd-fsck[878]: 0x25: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt
Nov 25 09:25:22 phoenix systemd-fsck[878]: Automatically removing dirty bit.
Nov 25 09:25:22 phoenix systemd-fsck[878]: Performing changes.
Nov 25 09:25:22 phoenix systemd-fsck[878]: /dev/nvme0n1p1: 34 files, 6897/51145 clusters
Nov 25 09:25:22 phoenix systemd-fsck[877]: boot: clean, 103/65536 files, 67833/262144 blocks