Skip to main content

create an LVM volume

Goal

On a machine with LVM installed I would like to create some more /tmp space

Recipe

Ask for information
   # vgs   VG    #PV #LV #SN Attr   VSize   VFree     scsi0   1   3   0 wz--n- 461,10G 195,10G   scsi1   1   1   0 wz--n- 931,51G  23,85G 
   # lvdisplay    ... 
Create the LVM according to the space left on the Volume group:
   #lvcreate  -L 200G scsi0 -n tmp   Logical volume "tmp" created 
 # lvdisplay  ...  --- Logical volume ---   LV Name                /dev/scsi0/tmp   VG Name                scsi0   LV UUID                ea10iW-wAnS-lUSA-clHW-X2M5-ibN3-uAUrws   LV Write Access        read/write   LV Status              available   # open                 0   LV Size                200,00 GB   Current LE             51200   Segments               1   Allocation             inherit   Read ahead sectors     auto   - currently set to     256   Block device           253:3 ... 
Format it
 # mkfs.ext3 /dev/scsi0/tmp 
Mount and use it
 # rm -rf /tmp/* ;  # mount -t ext3 /dev/mapper/scsi0-tmp /tmp 
Note: use "/dev/mapper/scsi0-tmp" not "/dev/scsi0/tmp"
To remove it
 # lvremove /dev/scsi0/tmp 

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs Pulumi LSP

Install Pulumi Emacs Mode The source code is on https://github.com/pulumi/pulumi-lsp. At the very bottom of the page are the instructions on how to install. You Need to have make installed. $ make install emacs-client mkdir -p ./bin go build -ldflags "-X github.com/pulumi/pulumi-lsp/sdk/version.Version=v0.2.3-6-gec49054" -o ./bin -p 10 ./cmd/... go: downloading github.com/pulumi/pulumi/sdk/v3 v3.53.1 ... ... ... go install -ldflags "-X github.com/pulumi/pulumi-lsp/sdk/version.Version=v0.2.3-6-gec49054" ./cmd/... mkdir -p editors/emacs/bin cd editors/emacs && emacs -Q --batch --eval "(progn (setq package-user-dir \"$(pwd)/bin\" \ package-archives '((\"melpa\" . \"https://melpa.org/packages/\") \