search for: 485m

I need to shrink /home(755G) to 150GB and use free space to add to the existing /(50G). #df -kh Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_web-lv_root 50G 7.8G 40G 17% / tmpfs 7.8G 384K 7.8G 1% /dev/shm /dev/sda2 485M 79M 381M 18% /boot /dev/sda1 200M 256K 200M 1% /boot/efi /dev/mapper/vg_web-lv_home755G 6.2G 711G 1% /home Need to have the step, can this be done online or need to go offline (umount) the file systems. Thanks

I installed Centos 6.x 64 bit with the minimal ISO and used two disks in RAID 1 array. Filesystem Size Used Avail Use% Mounted on /dev/md2 97G 918M 91G 1% / tmpfs 16G 0 16G 0% /dev/shm /dev/md1 485M 54M 407M 12% /boot /dev/md3 3.4T 198M 3.2T 1% /vz Personalities : [raid1] md1 : active raid1 sda1[0] sdb1[1] 511936 blocks super 1.0 [2/2] [UU] md3 : active raid1 sda4[0] sdb4[1] 3672901440 blocks super 1.1 [2/2] [UU] bitmap: 0/28 pages [0KB], 65536KB chunk md2 : a...

Hello, I did df -h on my CentOS 6.4 machine. $ df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_ysg-lv_root 47G 8.8G 36G 20% / tmpfs 948M 372K 947M 1% /dev/shm /dev/sda1 485M 62M 398M 14% /boot /dev/mapper/vg_ysg-lv_home 4.6G 2.7G 1.7G 63% /home What I don't understand is why is /home so tiny and how can I re-partition this without having to nuke and rebuild my machine?

...limit 0, 1 , According to google search, errorcode 28 means the HDD is full. But it isn't: root at vps:[~]$ df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 84G 18G 62G 23% / none 640M 0 640M 0% /dev/shm /usr/tmpDSK 485M 11M 449M 3% /tmp What else could cause this kind of problem? -- Kind Regards Rudi Ahlers CEO, SoftDux Hosting Web: http://www.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532

...D is full. But it >> isn't: >> >> >> root at vps:[~]$ df -h >> Filesystem ? ? ? ? ? ?Size ?Used Avail Use% Mounted on >> /dev/sda1 ? ? ? ? ? ? ?84G ? 18G ? 62G ?23% / >> none ? ? ? ? ? ? ? ? ?640M ? ? 0 ?640M ? 0% /dev/shm >> /usr/tmpDSK ? ? ? ? ? 485M ? 11M ?449M ? 3% /tmp >> >> >> What else could cause this kind of problem? > > You only have 449MB free on /tmp. It could easily fill that up during the > query, and then delete the file before you run df again. Run it while the > query is executing, I bet you see /tmp...

...d on the box to mount the LV, and specified the mount point as /. [root at earth ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_mei-lv_earthroot 5.0G 3.9G 880M 82% / tmpfs 5.9G 276K 5.9G 1% /dev/shm /dev/sda1 485M 116M 344M 26% /boot /dev/mapper/vg_mei-lv_earthvar 3.0G 748M 2.1G 27% /var /dev/mapper/vg_mei-lv_bacteriaroot 5.0G 3.9G 880M 82% / I tried to unmount the device, but as shown below, it is busy. [root at earth ~]# umount /dev/mapper/vg_mei-lv_ba...

...So then I switched over to the guest system and ran df -h to see the existing filesystem [root at guest1 jeffb]# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda2 4.5G 2.3G 2.0G 53% / tmpfs 1004M 88K 1004M 1% /dev/shm /dev/vda1 485M 30M 430M 7% /boot /dev/vdb1 2.0G 219M 1.7G 12% /var 6. Then I ran resize2fs /dev/vda2 and got the result that the filesystem is already xx blocks long. Nothing to do! So here is where I am stuck. Guest1 is my test system so it only has the / and /var logical volumes, wh...

Am 24.05.2017 um 17:50 schrieb Jeremy Allison via samba: > Here are some mitigation techniques from Red Hat in > case servers cannot be patched immediately: > 2. Mount the filessytem which is used by samba for its writeable share, > using "noexec" option. I would have expected this to be standard security precaution on all pure file servers (which is probably the most

...ted ?). I don't know where to start with this! Here are other informations: [root at radium data]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_radium-lv_root 50G 7.4G 40G 16% / tmpfs 5.9G 88K 5.9G 1% /dev/shm /dev/sda1 485M 92M 368M 21% /boot /dev/mapper/vg_radium-lv_home 437G 4.9G 410G 2% /home /dev/mapper/vg_radium2-lv_data 11T 6.1T 3.7T 63% /home/data [root at radium data]# uname -a Linux radium 2.6.32-279.19.1.el6.x86_64 #1 SMP Wed Dec 19 07:05:20 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux [root...

Greetings - I had a logical volume that was running out of space on a virtual machine. I successfully expanded the LV using lvextend, and lvdisplay shows that it has been expanded. Then I went to expand the filesystem to fill the new space (# resize2fs -p /dev/vde1) and I get the results that the filesystem is already xx blocks long, nothing to do. If I do a # df -h, I can see that the

Currently I''m trying to figure out the best zfs layout for a thumper wrt. to read AND write performance. I did some simple mkfile 512G tests and found out, that per average ~ 500 MB/s seems to be the maximum on can reach (tried initial default setup, all 46 HDDs as R0, etc.). According to http://www.amd.com/us-en/assets/content_type/DownloadableAssets/ArchitectureWP_062806.pdf I would