From Fedora Project Wiki
No edit summary
mNo edit summary
(28 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{QA/Test_Case
{{QA/Test_Case
|description=This test case ensures that disk drive(s) are properly unmounted during a shut-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 on a bare metal system.
# Install the pre-released version of Fedora to be tested. If you are installing from a LiveOS, perform the steps below with the LiveOS before doing the install. After this go ahead with the install. Then perform the steps below when the system is running from the hard drive.
# Reboot the system to the hard drive after the install.
# Reboot the system to the hard drive after the install.
{{admon/warning| Be sure to use a Bare Metal.}}


|actions=
|actions=
# 1. 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.
# 2. At the command prompt, issue the following command: journalctl -b /usr/lib/systemd/systemd-fsck
# At the command prompt, issue the following command: <pre>journalctl -b | grep -E "dirty bit|data may be corrupt|recovery|unmounted|recovering"</pre> There should not be any output.
# 3. Review the journal output
# If there has been output from the grep command, issue the following command {{command| journalctl -b -l > journal.log}} Please file a bug report and attach the journal.log file to the bug report.
# Restart the test system using the command {{command|reboot}} on the virtual console.
# Repeat steps 1 and 3 above.


# 5. You now need to manually re-boot the system. On most hardware (which complies with ACPI), you can manually power off by holding the power button down for five seconds. Then press the power button to power on again.
      Result: When the system boots, either after a halt, reboot or shutdown operation, the system successfully boots without error. All expected disk partitions are cleanly mounted. Check boot logs to see that they do not show any”fsck” (filesystem repair) operations, or “recovering journal” (ext3/4 journal recovery.  The boot logs only need to be checked after one shutdown - reboot cycle. The logs can be checked using the command “journalctl -b /usr/lib/systemd/systemd-fsck”. A result similar to the following indicates clean mounting:
“Example: -- Logs begin at Mon 2018-11-19 13:52:18 EST, end at Sat 2019-01-12 12:27:48 ES>
Jan 12 08:37:25 localhost.localdomain systemd-fsck[503]: /dev/mapper/fedora-roo>
Jan 12 08:37:36 localhost.localdomain systemd-fsck[745]: /dev/mapper/fedora-hom>
Jan 12 08:37:36 localhost.localdomain systemd-fsck[743]: /dev/sda1: clean, 412/>”
# 6. After the system boots, again change to a virtual console by pressing Ctrl+Alt+F2.
      Result: Virtual console appears
# 7. At the virtual console, login as the root user
      Result: Login successful
# 8. Reboot the system by running the command: “reboot”
      Result: The `reboot` is accepted and initiates a system reboot. The system reboots with no additional user interaction. Note: Manually booting the system may be required if the previous step fails.
# 9. After the system boots, once again change to a virtual console by pressing Ctrl+Alt+F2.
      Result: Virtual console appears.
# 10. At the virtual console, login as a non-root user. If no non-root user accounts are available, you can create a new user account as follows: Login as the root user and use the command: “useradd” to add a non-root user. Logout of root and login as the new non-root user.
      Result: User creation successful if used. Non-root login successful.
# 12. Power off the system by running the shutdown command. Consult the man page for different acceptable [TIME] values. For example, to power off the system immediately, type the following command: “shutdown now”
      Result: The shutdown is accepted and powers off the system without error.
# 13. Lastly, power on the system.  Check that it boots successfully.
      Result: When the system boots, either after a halt, reboot or shutdown operation, the system successfully boots without error, and all expected disk partitions are cleanly mounted.
|results=
|results=
# Good Result example: "Logs begin at Mon 2018-11-19 13:52:18 EST, end at Sat 2019-01-12 12:27:48 ES>
# The greps should not produce any output.
Jan 12 08:37:25 localhost.localdomain systemd-fsck[503]: /dev/mapper/fedora-roo>
Jan 12 08:37:36 localhost.localdomain systemd-fsck[745]: /dev/mapper/fedora-hom>
Jan 12 08:37:36 localhost.localdomain systemd-fsck[743]: /dev/sda1: clean, 412/>
# 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
}}
}}
[[Category:Base_Acceptance_Test_Cases]]
[[Category:Base_Acceptance_Test_Cases]]
[[Category:Package systemd test cases]]
[[Category:Package systemd test cases]]

Revision as of 16:30, 6 January 2020

Description

This test case ensures that disk drive(s) are properly unmounted during a power-down or a restart.

Setup

  1. Install the pre-released version of Fedora to be tested. If you are installing from a LiveOS, perform the steps below with the LiveOS before doing the install. After this go ahead with the install. Then perform the steps below when the system is running from the hard drive.
  2. Reboot the system to the hard drive after the install.

How to test

  1. On the running system, Switch to a free virtual console using Ctrl+Alt+F<n> shortcut and log in.
  2. At the command prompt, issue the following command:
    journalctl -b | grep -E "dirty bit|data may be corrupt|recovery|unmounted|recovering"
    There should not be any output.
  3. If there has been output from the grep command, issue the following command journalctl -b -l > journal.log Please file a bug report and attach the journal.log file to the bug report.
  4. Restart the test system using the command reboot on the virtual console.
  5. Repeat steps 1 and 3 above.

Expected Results

  1. The greps should not produce any output.