[Touch-packages] [Bug 1737582] Re: We have a server with a volume Group (VG) and two logical volumes (LV). About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "vg

We had to reinstall Ubuntu keeping the VG in order to make it work again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1737582 Title: We have a server with a volume

[Touch-packages] [Bug 1737965] Re: Error "stdin: fdopen failed: Invalid argument" while running lvreate, lvremove or lvs in a script run using nohup or scheduled in crontab

It seems a bug of LVM for Ubuntu 14. We found the solution thanks to this post: https://github.com/saltstack/salt/pull/9227 We run the script redirecting "/dev/null" to stdin for the script and now it works: nohup ./backup_zimbra_lvm.sh https://bugs.launchpad.net/bugs/1737965 Title: Error

[Touch-packages] [Bug 1737965] [NEW] Error "stdin: fdopen failed: Invalid argument" while running lvreate, lvremove or lvs in a script run using nohup or scheduled in crontab

Public bug reported: Error "stdin: fdopen failed: Invalid argument" while running lvreate, lvremove or lvs in a script run using nohup or scheduled in crontab When running "/sbin/lvcreate -L1M -s -n ZimbraBackup /dev/vg_opt-zimbra/lv_opt-zimbra", lvcreate returns these errors: stdin:

[Touch-packages] [Bug 1737582] Re: We have a server with a volume Group (VG) and two logical volumes (LV). About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "vg

** Description changed: Hi: We have a server with a volume Group (VG) and two logical volumes (LV). About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "vgs -a", but now nothing is shown. But if I run "lvs -a" or "vgs -a" or "lvdisplay" or

[Touch-packages] [Bug 1737582] Re: We have a server with a volume Group (VG) and two logical volumes (LV). About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "vg

Ubuntu versión is: #lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.4 LTS Release:14.04 Codename: trusty Version of lvm package is: # dpkg -l | grep lvm ii lvm2 2.02.98-6ubuntu2

[Touch-packages] [Bug 1737582] [NEW] We have a server with a volume Group (VG) and two logical volumes (LV). About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "

Public bug reported: Hi: We have a server with a volume Group (VG) and two logical volumes (LV). About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "vgs -a", but now nothing is shown. But if I run "lvs -a" or "vgs -a" or "lvdisplay" or "vgdisplay" I got

[Touch-packages] [Bug 1295596] Re: init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE

Hi: I have the same error on dmesg "init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE" We have a server with a volume Group (VG) and two logical volumes (LV). About two 11 days ago it worked fine and we could see information when we run "lvs -a" or "vgs -a". But if I