[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #24 from Andrius Štikonas --- (In reply to Laosom from comment #22) > I see. I will set up a Neon VM too with the similar FS layout. > Have you tested it yet ? So I was not able to reproduce this on Neon. But I agree that something is auto-mounting that partition on your disk. Unfortunately, I don't really know what. Maybe there are some clues in systemd .mount files? (that should be generated from your fstab). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #23 from Andrius Štikonas --- (In reply to Laosom from comment #22) > I see. I will set up a Neon VM too with the similar FS layout. > Have you tested it yet ? Sorry, not yet... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #22 from Laosom --- I see. I will set up a Neon VM too with the similar FS layout. Have you tested it yet ? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #21 from Andrius Štikonas --- (In reply to Laosom from comment #18) > journatctl shows no sign of udisks2 > > 2020. 07. 14. 18:12 systemd Stopped File System Check on > /dev/disk/by-uuid/e89658ee-a61a-49ce-bae0-d7463d1271bb. > 2020. 07. 14. 18:12 systemd Starting File System Check on > /dev/disk/by-uuid/e89658ee-a61a-49ce-bae0-d7463d1271bb... > 2020. 07. 14. 18:12 systemd Started File System Check Daemon to report > status. > 2020. 07. 14. 18:12 systemd-fsckvirtualmachines: clean, 34/3866624 > files, > 9188632/15440384 blocks > 2020. 07. 14. 18:12 systemd Started File System Check on > /dev/disk/by-uuid/e89658ee-a61a-49ce-bae0-d7463d1271bb. > 2020. 07. 14. 18:12 systemd Mounting /virtual_machines... > 2020. 07. 14. 18:12 kernel EXT4-fs (sda6): mounted filesystem with ordered > data mode. Opts: (null) > 2020. 07. 14. 18:12 systemd Mounted /virtual_machines. > 2020. 07. 14. 18:12 ksystemstatscould not find subsystem "pscount" > 2020. 07. 14. 18:12 plasmashell Model size of -2147483647 is less than 0 > 2020. 07. 14. 18:13 xdg-desktop-portal-kde xdp-kde-background: GetAppState > called: no parameters But I think it shows signs of systemd automounting sda6. Not sure why... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #20 from Laosom --- Created attachment 130120 --> https://bugs.kde.org/attachment.cgi?id=130120=edit kpart -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #19 from Laosom --- Created attachment 130119 --> https://bugs.kde.org/attachment.cgi?id=130119=edit journal -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #18 from Laosom --- journatctl shows no sign of udisks2 2020. 07. 14. 18:12 partitionmanager"Add operation: Shrink partition ‘/dev/sda6’ from 78,76 GiB to 58,90 GiB" 2020. 07. 14. 18:12 partitionmanager"Applying operations..." 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40090, resource id: 96469182, major code: 19 (DeleteProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40094, resource id: 96469182, major code: 18 (ChangeProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40101, resource id: 96469182, major code: 19 (DeleteProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40102, resource id: 96469182, major code: 18 (ChangeProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40103, resource id: 96469182, major code: 19 (DeleteProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40104, resource id: 96469182, major code: 19 (DeleteProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40105, resource id: 96469182, major code: 19 (DeleteProperty), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40106, resource id: 96469182, major code: 7 (ReparentWindow), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40107, resource id: 96469182, major code: 6 (ChangeSaveSet), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40108, resource id: 96469182, major code: 2 (ChangeWindowAttributes), minor code: 0 2020. 07. 14. 18:12 kwin_x11qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40109, resource id: 96469182, major code: 10 (UnmapWindow), minor code: 0 2020. 07. 14. 18:12 systemd Stopped File System Check on /dev/disk/by-uuid/e89658ee-a61a-49ce-bae0-d7463d1271bb. 2020. 07. 14. 18:12 systemd Starting File System Check on /dev/disk/by-uuid/e89658ee-a61a-49ce-bae0-d7463d1271bb... 2020. 07. 14. 18:12 systemd Started File System Check Daemon to report status. 2020. 07. 14. 18:12 systemd-fsckvirtualmachines: clean, 34/3866624 files, 9188632/15440384 blocks 2020. 07. 14. 18:12 systemd Started File System Check on /dev/disk/by-uuid/e89658ee-a61a-49ce-bae0-d7463d1271bb. 2020. 07. 14. 18:12 systemd Mounting /virtual_machines... 2020. 07. 14. 18:12 kernel EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null) 2020. 07. 14. 18:12 systemd Mounted /virtual_machines. 2020. 07. 14. 18:12 ksystemstatscould not find subsystem "pscount" 2020. 07. 14. 18:12 plasmashell Model size of -2147483647 is less than 0 2020. 07. 14. 18:13 xdg-desktop-portal-kde xdp-kde-background: GetAppState called: no parameters -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #17 from Andrius Štikonas --- (In reply to Eric S from comment #16) > Could it be udisks2 automounting the partition? Check journalctl... Hmm, good idea! Definitely worth checking. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #16 from Eric S --- Could it be udisks2 automounting the partition? Check journalctl... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 Andrius Štikonas changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #15 from Andrius Štikonas --- (changing bug state from needs info to reported.) -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #14 from Andrius Štikonas --- I can try to reproduce this on Neon Live USB (maybe next weekend if I don't forget). Although, it is likely that it will work there and this is some system misconfiguration (as I've said I don't understand what is mounting it, plasma automounter seems to be off). If I can't reproduce this, then maybe worth asking Neon developers? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #13 from Laosom --- Created attachment 129771 --> https://bugs.kde.org/attachment.cgi?id=129771=edit 20200629_2 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #12 from Laosom --- Created attachment 129770 --> https://bugs.kde.org/attachment.cgi?id=129770=edit 20200629_1 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #11 from Laosom --- As I wrote the filesystem is mounted back again after it was extended and that's the reason for the error. Of course I can run fsck if I unmount it manually before running it. I did and it works this way. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #10 from Andrius Štikonas --- (In reply to Laosom from comment #9) > I checked and find it was not running. ok. And can you run fsck manually afterwards? To see if it's still failing? As I've said before, maybe partition manager does not wait long enough for block device to get ready. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #8 from Laosom --- Created attachment 129702 --> https://bugs.kde.org/attachment.cgi?id=129702=edit PM error automounter -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #9 from Laosom --- I checked and find it was not running. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #7 from Andrius Štikonas --- (In reply to Laosom from comment #6) > I tried on ArcoB Plasma (5.19.2) and Manjaro KDE (5.18.5) latest. > It was OK. No issues, which was surprising , but delightful. > The resized ext4 filesystem was not in fstab. > > Retested in Neon. > The resized filesystem(s) were in fstab. Unmounted and commented out. > Same issue again. > One filesystem is used for timeshift backups the other one is for virtual > machines. > I wonder what Neon (ubuntu ?) is doing. Being in fstab shouldn't really be that important in this case (it may only be indirectly affecting this. For example if automounter reads fstab and mounts everything there)... Could you check what happens with plasma automounter on Neon. (You can see its status in System Settings -> Startup and shutdown -> Background services). If it is running, partitionmanager should stop it automatically using dbus). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #6 from Laosom --- I tried on ArcoB Plasma (5.19.2) and Manjaro KDE (5.18.5) latest. It was OK. No issues, which was surprising , but delightful. The resized ext4 filesystem was not in fstab. Retested in Neon. The resized filesystem(s) were in fstab. Unmounted and commented out. Same issue again. One filesystem is used for timeshift backups the other one is for virtual machines. I wonder what Neon (ubuntu ?) is doing. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #5 from Laosom --- I tried again. Dolphin was not open. I unmounted in PM. Same behaviour. I am running KDE Neon 5.19.2 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #4 from Andrius Štikonas --- (In reply to Laosom from comment #3) > Hi Andrius, > > No matter how I unmount the FS. I did it within Partition Manager and in > Dolphin too. > I did not try fsck manually afterwards, as the filesystem was mounted after > resize by Partition Manager. I assume it is successful if the FS is not > mounted. That is very strange. The filesystem should stay unmounted whether successful or not. KDE Partition Manager would not automount ext4. (It does automount some other filesystems like btrfs that can only be resized when mounted but not ext4.) Maybe something else is automounting fs on your system and interfered with resize2fs command? That might explain why there are fsck errors afterwards. I'm not sure what could be automounting. Partition Manager does try to disable KDE automounter. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #3 from Laosom --- Hi Andrius, No matter how I unmount the FS. I did it within Partition Manager and in Dolphin too. I did not try fsck manually afterwards, as the filesystem was mounted after resize by Partition Manager. I assume it is successful if the FS is not mounted. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Andrius Štikonas --- . -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 423397] fsck fails after shrinking ext4 fs
https://bugs.kde.org/show_bug.cgi?id=423397 --- Comment #1 from Andrius Štikonas --- I'm not sure I fully understand your steps to reproduce. Did you unmount ext4 filesystem inside partitionmanager? What happens if you run e2fsck -f -y -v /dev/sda6 manually later? (I'm asking this to determine if fsck failure is just because of some race condition, maybe block device was not ready yet after sfdisk resized it). -- You are receiving this mail because: You are watching all bug changes.
