Markus:
Looking back at an earlier version of my script that I was using when I first
reported this bug, I used to do exactly what you describe: umount'ing all the
partitions before doing any lvremove on any partition. Now I umount and
lvremove each partition before proceeding to the next partition. It does seem
to point the finger at umount rather than lvremove.
I do not run the scipt in the context of bacula-fd. That is to say, it
is not a bacula RunBefore or RunAfter script. I'm assuming that's what
you meant. Instead, I have a cron job bourne shell script which does
all of the commands that are external to bacula (lvcreate, mount,
umount, lvremove, etc), and uses bconsole only to do the bacula backup
job. So it looks like this:
...postgresql stuff...
...lvcreate...
...mount...
sudo -E -u bacula /usr/bin/bconsole -c /etc/bacula/bconsole.conf <<EOF
@output /dev/null
messages
@tee "${TMP_LOG}"
run job=brain-all-job client="${CLIENT}" level="${BACKUP_LEVEL}"
pool="${BACKUP_POOL}" yes
wait jobname=brain-all-job
messages
@output
quit
EOF
...umount...
...lvremove...
So the bug is occuring for me in the context I've shown above.
Previously I had inserted some code in the scipt to try to fix and/or
debug the problem, and then have since commented it out. I was
unsuccesful before, but will try again. This is what I had in the
script. If anyone has any additional debugging suggestions, please
advise:
# time -p udevadm settle
# logger --priority syslog.info --stderr --tag "`basename ${0}`" "umount'ing
${i}"-snap
# blockdev --report /dev/volgroup0/"${i}"-snap /dev/volgroup0/"${i}"
/dev/mapper/volgroup0-"${i}"*
# time -p sync
# blockdev --flushbufs /dev/volgroup0/"${i}"-snap /dev/volgroup0/"${i}"
/dev/mapper/volgroup0-"${i}"*
# Could also try disabling journal using tune2fs??
# cat /proc/locks > /etc/bacula/debugLocks.txt
# echo >> /etc/bacula/debugLocks.txt
# ps axl >> /etc/bacula/debugLocks.txt
# echo >> /etc/bacula/debugLocks.txt
# fuser -mv /mnt/"${i}"-snap >>/etc/bacula/debugLocks.txt
sync
umount /mnt/"${i}"-snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115753
Title:
Umount of Multiple LVM Snapshots Causes 'soft lockup CPU#0 stuck for'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1115753/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
