[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

[Sistemas]

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 </dev/null &

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1737965

Title:
  Error "stdin: fdopen failed: Invalid argument" while running lvreate,
  lvremove or lvs in a script run using nohup or scheduled in crontab

Status in upstart package in Ubuntu:
  New

Bug description:
  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 -L10000M -s -n ZimbraBackup /dev/vg_opt-zimbra/lv_opt-zimbra", lvcreate returns these errors:
    stdin: fdopen failed: Invalid argument
    stdin: fclose failed: Invalid argument
    stdin: fdopen failed: Invalid argument

  When running "/sbin/lvremove --force /dev/vg_opt-zimbra/ZimbraBackup", lvremove returns these errors:
    stdin: fdopen failed: Invalid argument
    stdin: fclose failed: Invalid argument
    stdin: fdopen failed: Invalid argument

  
  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 amd64 Linux Logical Volume Manager


  In Ubuntu 16 it works fine, but in Ubuntu 14 it doesn't.

  Is it a bug?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1737965/+subscriptions