Skip to main content

create an LVM volume


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


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='' 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=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found 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='

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl= " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme. I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create. Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard: "Create with shared configuration" will allow me to select the project I want the new one to share configuration with. The new created project will use the same configuration as the project I select There will be no creation of Workflow and Issue Scheme that