Hi Rafael Everything was working ok until just before I had done the reboot - the seeming first problem was Windows clients having permission issues writing to the folders on ocfs2 filesystem, then the reboot led to the no free space messages.
DRBD has had no issues so far, and having brought the server down for a period of time I was still able to re-sync ok despite the ocfs2 problems, although that sync didn't affect the file system on the remote server. I haven't tried to deploy any other file system types, so that's a test I will do today. Here's the apt log for 8th September: Start-Date: 2020-09-08 18:25:32 Commandline: apt dist-upgrade Requested-By: richard (1000) Install: linux-modules-extra-5.4.0-47-generic:amd64 (5.4.0-47.51, automatic), linux-headers-5.4.0-47-generic:amd64 (5.4.0-47.51, automatic), motd-news-config:amd64 (11ubuntu5.2, automatic), linux-modules-5.4.0-47-generic:amd64 (5.4.0-47.51, automatic), linux-headers-5.4.0-47:amd64 (5.4.0-47.51, automatic), linux-image-5.4.0-47-generic:amd64 (5.4.0-47.51, automatic) Upgrade: libpam0g:amd64 (1.3.1-5ubuntu4, 1.3.1-5ubuntu4.1), libirs-export161:amd64 (1:9.11.16+dfsg-3~build1, 1:9.11.16+dfsg-3~ubuntu1), linux-headers-generic:amd64 (5.4.0.45.49, 5.4.0.47.50), ipxe-qemu:amd64 (1.0.0+git-20190109.133f4c4-0ubuntu3, 1.0.0+git-20190109.133f4c4-0ubuntu3.2), alsa-ucm-conf:amd64 (1.2.2-1ubuntu0.1, 1.2.2-1ubuntu0.2), libpam-modules:amd64 (1.3.1-5ubuntu4, 1.3.1-5ubuntu4.1), grub-common:amd64 (2.04-1ubuntu26.2, 2.04-1ubuntu26.3), linux-image-generic:amd64 (5.4.0.45.49, 5.4.0.47.50), libasound2-data:amd64 (1.2.2-2.1ubuntu1, 1.2.2-2.1ubuntu2), sudo:amd64 (1.8.31-1ubuntu1, 1.8.31-1ubuntu1.1), ubuntu-standard:amd64 (1.450.1, 1.450.2), grub2-common:amd64 (2.04-1ubuntu26.2, 2.04-1ubuntu26.3), ubuntu-server:amd64 (1.450.1, 1.450.2), libpam-runtime:amd64 (1.3.1-5ubuntu4, 1.3.1-5ubuntu4.1), libisc-export1105:amd64 (1:9.11.16+dfsg-3~build1, 1:9.11.16+dfsg-3~ubuntu1), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), ubuntu-minimal:amd64 (1.450.1, 1.450.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), grub-efi-amd64-bin:amd64 (2.04-1ubuntu26.2, 2.04-1ubuntu26.3), python3-distupgrade:amd64 (1:20.04.23, 1:20.04.25), libpulse0:amd64 (1:13.99.1-1ubuntu3.5, 1:13.99.1-1ubuntu3.6), python3-commandnotfound:amd64 (20.04.2, 20.04.4), libisccfg-export163:amd64 (1:9.11.16+dfsg-3~build1, 1:9.11.16+dfsg-3~ubuntu1), ubuntu-release-upgrader-core:amd64 (1:20.04.23, 1:20.04.25), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libpulse-mainloop-glib0:amd64 (1:13.99.1-1ubuntu3.5, 1:13.99.1-1ubuntu3.6), debootstrap:amd64 (1.0.118ubuntu1.1, 1.0.118ubuntu1.2), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), libpam-modules-bin:amd64 (1.3.1-5ubuntu4, 1.3.1-5ubuntu4.1), bcache-tools:amd64 (1.0.8-3, 1.0.8-3ubuntu0.1), grub-efi-amd64:amd64 (2.04-1ubuntu26.2, 2.04-1ubuntu26.3), libdns-export1109:amd64 (1:9.11.16+dfsg-3~build1, 1:9.11.16+dfsg-3~ubuntu1), libasound2:amd64 (1.2.2-2.1ubuntu1, 1.2.2-2.1ubuntu2), grub-efi-amd64-signed:amd64 (1.142.4+2.04-1ubuntu26.2, 1.142.5+2.04-1ubuntu26.3), unattended-upgrades:amd64 (2.3, 2.3ubuntu0.1), command-not-found:amd64 (20.04.2, 20.04.4), tmux:amd64 (3.0a-2, 3.0a-2ubuntu0.1), linux-firmware:amd64 (1.187.2, 1.187.3), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), fonts-noto-mono:amd64 (20200323-1, 20200323-1build1~ubuntu20.04.1), linux-generic:amd64 (5.4.0.45.49, 5.4.0.47.50), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), base-files:amd64 (11ubuntu5.1, 11ubuntu5.2) End-Date: 2020-09-08 18:31:54 Start-Date: 2020-09-08 18:37:03 Commandline: apt autoremove Requested-By: richard (1000) Remove: linux-headers-5.4.0-42-generic:amd64 (5.4.0-42.46), linux-modules-5.4.0-42-generic:amd64 (5.4.0-42.46), linux-headers-5.4.0-42:amd64 (5.4.0-42.46), linux-image-5.4.0-42-generic:amd64 (5.4.0-42.46), linux-modules-extra-5.4.0-42-generic:amd64 (5.4.0-42.46) End-Date: 2020-09-08 18:37:28 You can see that the newly installed kernel header/modules/image are 5.4.0-47 and the ones I got rid of by autoremove were 5.4.0-42. However, there was an unattended upgrade on 3rd Sept in which 5.4.0-45 had been installed, so this is likely the previously used kernel version. I'll report soon on the alternative file system as well as booting to the previous kernel version. ------------------------------------------------------------------------ Richard Andrew Davel Technology T: 01786 448007 M: 07813 298095 On 14/09/2020 14:35, Rafael David Tinoco wrote: > Hello Richard, > > Do you know which kernel you were using before the reboot ? Was > everything working as expected before this upgrade/reboot action ? > > What packages were upgraded ? (you can check in apt history). > > What if you move back to the kernel you were, can you create the > filesystem ? Does it mitigate the issue ? > > Are you having any problems with DRBD ? Is it fully sync'ed ? Are you > able to create other filesystems on top of the DRBD volume with no > issues ? > > I'm flagging this as incomplete until you provide more information. Feel > free to move this back to New so we can re-triage this accordingly. > > > ** Changed in: ocfs2-tools (Ubuntu) > Status: Triaged => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895526 Title: ocfs2 file system no longer write - "disk full" despite lots of free space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1895526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
