-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeout formatting volume #60
Comments
Hi kurtharriger Mixlib::Shellout accepts a time out argument so there is a way. Depending on what you need, a temporary solution, a permanent solution, widespread fix or not you might try one of these.
I didn't see anything built in to the current lvm code designed to do what you want. Regards, |
The workaround I came up with was to explicitly format the volume with an execute statement. lvm_logical_volume will detect that it has already been formatted and just configure fstab and mount point. execute 'format' do |
scratch that executing format explicitly only worked since the device already existed from failed run. Running on new machine failed since device had not yet been created. |
I'd like to request a |
Is there any way to increase the timeout? Looks like mkfs.ext4 is taking more than 5 minutes to format a 1000Gb ebs volume.
Mixlib::ShellOut::CommandTimeout
--------------------------------
Command timed out after 600s:
Command exceeded allowed execution time, process terminated
---- Begin output of yes | mkfs -t ext4 /dev/mapper/graphite-data ----
STDOUT: Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
65536000 inodes, 262142976 blocks
13107148 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
8000 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
The text was updated successfully, but these errors were encountered: