From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 8: | Line 8: | ||
# 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 -l > journal.txt}} | # At the command prompt, issue the following command {{command| journalctl -b -l > journal.txt}} | ||
# <pre> At the command prompt, issue the following command journalctl -b | grep 'dirty bit' | # <pre> At the command prompt, issue the following command journalctl -b | grep 'dirty bit' | 'data may be corrupt' | 'recovery'</pre> | ||
# At the command prompt, issue the following command{{command| grep 'unmounted' journal.txt}} | # At the command prompt, issue the following command{{command| grep 'unmounted' journal.txt}} | ||
# At the command prompt, issue the following command{{command| grep 'recovering' journal.txt}} | # At the command prompt, issue the following command{{command| grep 'recovering' journal.txt}} |
Revision as of 19:01, 6 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. 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
- 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 -l > journal.txt
At the command prompt, issue the following command journalctl -b | grep 'dirty bit' | 'data may be corrupt' | 'recovery'
- At the command prompt, issue the following command
grep 'unmounted' journal.txt
- At the command prompt, issue the following command
grep 'recovering' journal.txt
- There should not be any output from any of the grep commands. If there has been any output from any of the grep commands, file a bug report and attach the journal.txt file to the report.
- Close the Journal output and restart the test system using the command
reboot
on the virtual console. - Repeat steps 3 through 8 above.
Expected Results
- The greps should not produce any output.