| Summary: | "Performing unsafe table load" error during snapshot creation | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Olivier Fabre <axel.foster-5bcwppg> |
| Component: | lvm2 | Assignee: | Alasdair Kergon <agk> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | agk, bmarzins, bmr, dwysocha, heinzm, jonathan, lvm-team, mbroz, msnitzer, prajnoha, prockai, spacewar, zkabelac |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.87-1.fc17 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-02-02 11:36:29 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Olivier Fabre
2011-07-24 22:43:29 UTC
Something that may or may not be related, I see this in my dmesg: [127321.472643] dmeventd (10022): /proc/10022/oom_adj is deprecated, please use /proc/10022/oom_score_adj instead. [127321.565209] EXT4-fs (dm-2): write access unavailable, skipping orphan cleanup [127321.565211] EXT4-fs (dm-2): recovery complete [127321.565215] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [127381.802423] EXT4-fs warning (device dm-0): release_blocks_on_commit:2679: discard not supported, disabling [128438.838490] EXT4-fs warning (device dm-1): release_blocks_on_commit:2679: discard not supported, disabling [128438.866990] EXT4-fs (dm-2): write access unavailable, skipping orphan cleanup [128438.866992] EXT4-fs (dm-2): recovery complete [128438.866996] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) I don't know when it happened exactly, but nothing more is added to dmesg when I perform the lvcreate command mentionned in the bug report (or the subsequent lvremove.) I have no "dm-2" in /dev. My fstab contains: /dev/VGSSD1/ArchRoot64 / ext4 noatime,discard,commit=60,errors=remount-ro 0 1 /dev/VGSSD1/ArchRoot /mnt/arch32 ext4 noatime,discard,commit=60,errors=remount-ro 0 1 and "mount" says: /dev/VGSSD1/ArchRoot64 on / type ext4 (rw,noatime,errors=remount-ro,user_xattr,acl,commit=60,barrier=1,data=ordered,discard) /dev/mapper/VGSSD1-ArchRoot on /mnt/arch32 type ext4 (rw,noatime,discard,commit=60,errors=remount-ro) Amazing. Reproduced... This patch does remove the error message. About my previous comment about not having any dm-2, I was wrong of course: there is dm-2 in /dev when the snapshot is created: $ l /dev/mapper/ total 0 lrwxrwxrwx 1 root 7 Jul 25 03:27 VGSSD1-ArchRoot -> ../dm-0 lrwxrwxrwx 1 root 7 Jul 25 03:27 VGSSD1-ArchRoot-real -> ../dm-3 lrwxrwxrwx 1 root 7 Jul 25 03:19 VGSSD1-ArchRoot64 -> ../dm-1 lrwxrwxrwx 1 root 7 Jul 25 03:27 VGSSD1-lvm_backup_snapshot -> ../dm-2 lrwxrwxrwx 1 root 7 Jul 25 03:27 VGSSD1-lvm_backup_snapshot-cow -> ../dm-4 I guess that explains the "write access unavailable" messages by ext4, since dm-2 is a read-only snapshot. Still slightly worried about the "discard not supported, disabling" message on dm-0... But that's unrelated to this bug I suppose. (I think it happens the first time the snapshot is created.) (In reply to comment #4) > Still slightly worried about the "discard not supported, disabling" message on > dm-0... But that's unrelated to this bug I suppose. (I think it happens the > first time the snapshot is created.) This is due to the fact that the snapshot-origin target doesn't support discards. And ext4 will disable discards as soon as a discard request fails. Please see: http://www.redhat.com/archives/dm-devel/2011-April/msg00147.html AFAIK that ext4 commit still hasn't been reverted or the relevant coded tweaked to simply warn without disabling discard. Got the same error creating a snapshot with F16, lvm2-2.02.86-5.fc16.x86_64. To clarify, the error I got is "Internal error: Performing unsafe table load while 2 device(s) are known to be suspended: (253:7)". I do have a "write access unavailable" message in /var/log/messages, which may or may not be related. I don't see any messages about "discard not supported". It would be really nice if instead of just changed to "closed rawhide", there was a brief explanation of what has changed that has fixed it. That would make it easier for bug reporters to make sure that they get the appropriate package and confirm that it is fixed. (In reply to comment #8) > It would be really nice if instead of just changed to "closed rawhide", there > was a brief explanation of what has changed that has fixed it. That would make > it easier for bug reporters to make sure that they get the appropriate package > and confirm that it is fixed. The warning message "Performing unsafe table load" is not (incorrectly) issued anymore when creating a read-only snapshot (comment #3 referencing the fix and comment #4 confirming this the fix that the reporter expects). The package this was fixed in is lvm2-2.02.87-1.fc17. |