| Summary: | Installing big package-collections results in read-only file system | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | AlbinLOtterhaell |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | AlbinLOtterhaell, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-27 13:51:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
There isn't enough information to look at this bug. At a minimum, there should be an error message in dmesg when the filesystem switches to read-only unless there is a scriptlet in the installed set of packages that is doing it via userspace. Could you try this again and then attach the full dmesg output after the issue occurs? I've no idea that commands and logs to copy, so could you write down the commands and logs that should give you the information you need? I can reproduce it, just need to know what to do. Reproduce your problem however you have been, then run 'dmesg > dmesg.txt' as root in a shell and then attach the resulting dmesg.txt file to bugzilla. |
Description of problem: Then installing a big application, the file system becomes read-only after installing little over one thousand of the packages. Version-Release number of selected component (if applicable): Fully updated Fedora 23 How reproducible: Always (didn't happen one-time, more info in 'Additional info') Steps to Reproduce: 1. Run '# dnf install texlive-scheme-full' Actual results: File system (EXT4) becomes read-only. Expected results: Installation complete without failure, and file system remain able to read and write to the disk. Additional info: No bad blocks on my SSD according to '# badblocks -v /dev/sda' and '# badblocks -w -v /dev/sda'. I had this problem several times (re-installed Fedora 23 x times). It worked one-time without this problem. I think I started the installation of 'texlive-scheme-full' and didn't do anything else but to stop the display to dim by moving the pointer. The first times I only needed to reboot the computer and the installation finished without any hickups. But the last time the system totally crashed and had no other option than to reinstall Fedora. I have run CentOS 7 and (currently) Fedora 22, which works without any problem. Tested with booth BIOS and UEFI. Always tested with an encrypted drive. As noted before, using EXT4 file system. $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 223.6G 0 disk ├─sda1 8:1 0 200M 0 part /boot/efi ├─sda2 8:2 0 500M 0 part /boot └─sda3 8:3 0 222.9G 0 part └─luks-[...] 253:0 0 222.9G 0 crypt ├─fedora_laptop--0-swap 253:1 0 16G 0 lvm [SWAP] ├─fedora_laptop--0-00 253:2 0 20G 0 lvm / └─fedora_laptop--0-home 253:3 0 186.9G 0 lvm /home I don't know if it's related, but I can't download bigger files without it become read-only when I use a liveUSB.