I have been asked to use space allocated to /dev/sdb2 to grow /dev/sdb1 both filesystems contain data. When I run lvdisplay or vgdisplay I get "no volume groups found". and pvdisplay returns nothing. Do I need to add the fs to a group?
View 2 RepliesI have let the debian installer set up with separate partions forrootusrvarhometmpIt ended up with a huge home partition and little place for the others.So I wanted to give some of home's space to the others and didlvreduce on homelvextend on the others.Following some info on the net it tells you toe2fsck -f partition1 followed by aresize2fs partition1But when I try to fsck the reduced home partition I got the following error:The filesystem size (according to the superblock) is 73113600 blocksThe physical size of the device is 20447332 blocksEither the superblock or the partition table is likely to be corrupt!Abort? yesIs there any way to save this?
View 5 Replies View Relatedi cannot resize mounted lvm volumes with reiserfs by using yast like in a previous version 10.x !?
View 6 Replies View Relatedi have a fedora 11 server which can't access the ext4 partitions on lvm logical volumes on a raid array during boot-up. the problem manifested itself after a failed preupgrade to fedora 12; however, i think the attempt at upgrading to fc12 might not have anything to do with the problem, since i last rebooted the server over 250 days ago (sometime soon after the last fedora 11 kernel update). prior to the last reboot, i had successfully rebooted many times (usually after kernel updates) without any problems. i'm pretty sure the fc12 upgrade attempt didn't touch any of the existing files, since it hung on the dependency checking of the fc12 packages. when i try to reboot into my existing fedora 11 installation, though, i get the following screen: (click for full size) a description of the server filesystem (partitions may be different sizes now due to the growing of logical volumes):
Code:
- 250GB system drive
250MB/dev/sdh1/bootext3
lvm partition rest of driveVolGroup_System
10240VolGroup_System-LogVol_root/ext4
[code]....
except he's talking about fake raid and dmraid, whereas my raid is linux software raid using mdadm. this machine is a headless server which acts as my home file, mail, and web server. it also runs mythtv with four hd tuners. i connect remotely to the server using nx or vnc to run applications directly on the server. i also run an xp professional desktop in a qemu virtual machine on the server for times when i need to use windows. so needless to say, it's a major inconvenience to have the machine down.
I'm using ubuntu 10.10.While I installed it in my desktop, i choose double boot by selecting "install them side by side,choosing between them each start up". After installing I found that my ext4 with root size is 100GB and swap 4 GB. Isn't it too big!!?? Is there any way to reduce the size of ext4 with root without harming the OS? Should it be done?
View 5 Replies View RelatedI created only two partitions, root and /home. I want to resize root to a bigger value. I tried to play a little with parted without result. How can I do it safely?
View 6 Replies View RelatedHow do I resize an ext4 partition including moving the start address? Actually what I want to do is extend the partition in front of it but that means first making space between partitions 1 and 2.As best I can tell resize2fs will resize the partition but not let me move the start addres. And fdisk will run, on say /dev/sda3 (the one I want to resize), but its default display doesn't show a start and end address which leads me to believe that fdisk isn't going to do what I want either.
View 8 Replies View RelatedI have a dual boot system with Ubuntu Lucid and Windows 7 Ultimate 32bit on a 320 GB hard drive. During the last month, I've completely moved from Windows to Ubuntu but I have to keep Windows for a few softwares like ooVoo and Office, especially OneNote. But now 105 GB for windows and 50 GB for Ubuntu doesn't seems right, as I can't copy any more files on my Desktop in Ubuntu, because it's full. I was just wondering if it's possible to resize the NTFS partition and add like 50GB or so to the ext4 partition which is my Linux's root. The NTFS drive is on /dev/sda5 and the ext4 one is on /dev/sda7.
View 4 Replies View RelatedI didn't know a resize operation on a 750 GB disk was going to take 40+ hours, and I was biting my nails the whole time, until the power went out when "only" 8 hours where left.I can still mount the partition, and many of the files are still there, but some files show as '? ? ? ? ? filename.ext' with ls -l.If I try to go inside such a directory: Input/output error.
View 1 Replies View RelatedIs it possible to partition an LVM in two volumes. So that one can be an ext4 filesystem and another can be swap.
View 6 Replies View RelatedLooking at the output of a cat /proc/mdstat, how do i know what volumes its actually resyncing? when i do a df -h everything appears to be there.
Personalities : [raid1]
read_ahead 1024 sectors
Event: 2
md0 : active raid1 sdb1[1] sda1[0]
859549696 blocks [2/2] [UU]
[Code]....
Are there any maximum amount of logical volumes a LVM2 volume group can contain?
View 1 Replies View RelatedI'm using munin to monitor our servers. Recently I created additional partitions on one of them and I noticed that munin has not picked up the changes.
I restarted munin-node and running the plugin manually as user munin on the machine
Code:
$ munin-run df
I get all my partitions
Also when I telnet 10.1.1.25 4949 and run
Code:
fetch df
I'm getting all of them. The graph however displays only the ones that were there at the time of munin install.
How can I get munin to add the new partitions to the graph ?
I'm setting up two media servers - one will be primary and the second will be the failover box if the first one dies. My original plan was to use Heartbeat and DRBD to replicate the first to the second, but it turns out DRBD has a limitation of 16TB per volume, and my RAID 6 is 30TB in size. I'm trying to figure out some options.
One is to split the partition into two, so it's under the 16TB limit of DRBD, share both partitions, and then use LVM to join them as a single volume at the OS level. I'm not sure what kind of performance hit that will make on read/write access since now it will need to go through LVM *and* DRBD.
Two is to use something like GlusterFS or XtreemFS. However, I am wary of both of those as the first is a FUSE-based system and isn't really tuned for performance, and XtreemFS is still kind of beta-ish.
Three is good old rsync, but that is a bit too asynchronous in my opinion. I'd like to be able to fail over virtually instantly and not lose any content.This is a production system and performance of the disk systems are paramount, followed by reliability.
I'm trying to make a fresh install of Ubuntu 10.10 Server 64bit but is stuck with the Partitioning Disk part and Ubuntu 10.04 LTS provides the same error. The installation wizard gives me a menu:
!! Partitioning disks
This menu allows you to configure iSCSI volumes
iSCSI configuration actions
[code].....
We have a Centos 5.6 server mounting two iSCSI volumes from an HP P2000 storage array. Multipathd is also running, and this has been working well for the few months we have been using it. The two volumes presented to the server were created in LVM, and worked without problem.We had a requirement to reboot the server, and now the iSCSI volumes will no longer mount. From what I can tell, the iSCSI connection is working ok, as I can see the correct sessions, and if I run 'fdisk -l' I can see the iSCSI block devices, but the O/S isn't seeing the filesystems. Any LVM command does not show the volumes at all, and 'vgchange -a y' only lists the local boot volume, not the iSCSI volumes. My concern is that, the output of 'fdisk -l' says 'Disk /dev/xxx doesn't contain a valid partition table' for all the iSCSI devices. Research shows that performing the vgchange -a y command should automatically mount any VG's that aren't showing, but it doesn't work.
There's a lot of data on these iSCSI volumes, and I'm no LVM expert. I've read that some have had problems where LVM starts before iSCSI and things get a bit messed up, but I don't know if this is the case here (I can't tell), but if there's a way of switching this round that might help, I'm prepared to give it a go.There was absolutely no indication there were any problems with these volumes, so corruption is highly unlikely.
what the maximum number of logical volumes is for a volume group in LVM ? Is there any known performance hit for creating a large number of small logical volumes vs a small number of large volumes ?
View 1 Replies View RelatedI got a problem booting ubuntu 10.4 RC but i solved it by replacing root partirion uuid in grub boot menu then I disapled totally uuid passing to linux from /etc/default/grub . but something else i noticed why grub choosed insmod=ext2 why not ext4 specially I use now ext4 .I tried by editing the grub boot menu replacing "insmod=ext2" by "insmod=ext4" it booted and the three lines error during booting that i used to see them science ubuntu 9.10 totally disappeared . really I dont understand can anybody explane for me.and if what i did was right ,can anybody tell me how to make grub always and permenantly detect ext4 as ext4 not as ext2.
View 6 Replies View RelatedI had 5.4 machine. Upgraded to 5.5 today via yum upgrade. All went fine. Rebooted. Wanted to convert root partition to ext4 (I have three partitions: /boot, / and swap). All of them on software RAID 1 (root is /dev/md2). I did the following for converting
yum install e4fsprogs
tune2fs -O extents,uninit_bg,dir_index /dev/md2
nano /etc/fstab # I indicated here that my /dev/md2 is of ext4
[code]....
On recomendation from the team installing the DB on our new server, all the partitions etc on our VM were created as LVM's. The setup for this is like this:
Disk 1
-> /boot
-> /swap
-> LVMpartition1
[Code]....
I'm trying to run Firefox 3 in a VNC server without a window manager, since I don't want Firefox window chrome. My only problem is that I can't figure out how to resize Firefox. There are parameters to specify width and height, but they don't work (#5104). Please, are there any solutions?
Another question: VNC server seems to run twm, even though it isn't installed. How is that possible?
I'm using Ubuntu Server 9.04.
Googling tells you how to resize RAID partitions but not how to resize the underlying disk partitions. In my particular case, I initially sized a RAID array way too large - and when I added another disk to the array, I decided I was wasting too much space.I shrunk the file system, then "grew" the array (/dev/md2) to the smaller size, and resized the file system again to fit. However the actual disk partitions (/dev/sda2, /dev/sdb2, etc.) are still the original size - they are just mostly unused space.As I understand it, the superblocks are at the end of the partition. I believe this means the end of space used by the array on each device, so that the superblock moved to a lower block number when I shrunk the array. However it also means that I need to get the new physical partition size correct to avoid clobbering the superblock.
Is there an easy way to get any partition editor to shrink the physical partitions to the new array size?If not, is the superblock included in the space allocated to the array so that the next partition can start in the very next block, or is it added after the array so I'd need to allow some space for it?
I'm sure many of you here have worked with disk quotas and lvm2 and my problem involves both. Basically what I'm wanting to do is have it so whenever a logical volume gets below a certain constraint (10Gb's) ie. it only has that much left - I want to automatically resize it to add 20 GB's. Obviously this can be done rather easily manually, and with a bit of python hacking it can be done programmatically but since this is for production use I was wondering if there was something a bit more fluid. Since this server is I/O intensive ZFS implemented via FUSE is not an option and neither is the still unstable BtrFS.
View 3 Replies View RelatedI have a 6 disk machine, i am using FC12, i created a software raid 5 device /dev/md1
i formatted it
Code:
mkfs.ext4 /dev/md1
and mounted with options as so:
[Code]...
I have installed 2 extra 1.5TB drives on a stable Centos 5.5 system. They are set up with 2 unequal partitions on each - with 2 raid 1 arrays. The largest of the raid arrays is used as a new volgeoup with 2 unequal LVMs. The larger of the LVMs is around 1.3TB. I installed an ext4 filesystem (default parameters) on the larger LVM.I went to mount the LVM - the system hung. No keyboard or network response and no response to the soft shutdown button.It was the deadest I have ever seen it - and this system has been incredibly stable.
In the absence of any other suspects - I am tempted to blame ext4 - since I have never used it before - and since wikapeadia tells me ext4 isn't supposed to be in the 2.6.8 kernels...:
[URL]
I will do some more testing on this tomorrow to try to confirm my suspicions. I will try to repeat the crash - then try mounting it as ext3 to see if it behaves differently. Any other tests I should do?What is the status of ext4 in RHEL5.5. Has it been added to the 2.6.18 kernel by RH? Is this what is meant by a "back port"?
I am running CentOS 5.5 with a 14T ext4 volume. We are sharing out a few sub-directories via NFS. Our customer was doing some penetration testing with our web app that writes to one of those NFS shares. We are not sure if they did something to cause the metadata to grow so large or if it is corrupt. Here is the listing:drwxrwxr-x 1 owner owner 470M Jun 24 18:15 temp.badI guess the metadata could actually be that large, however we have been unable to perform any operations on that directory to determine if the directory is just loaded with files or corrupted. We have not run an fsck on the volume because we would need to schedule downtime for out customers to do so. Has anyone come across this before
View 2 Replies View RelatedCan windows read files from a home file server with an ext4 file system? or do I have to partition the drive with the server (ext4) and an ntfs partition with the files on?
View 4 Replies View RelatedSummary of issue: EXT4 filesystem won't mount--with error = mount: unknown filesystem type 'ext4'. Is no ext4 in kernel the issue? Or is something corrupted?Really perplexed by this. I updated Centos 5.5 to 5.6 to get ext4 (5.6 is supposed to have full support of ext4). I built several arrays and put the ext4 filesystem on them. All went well until I tried to mount them. BTW, this array (below) is set up as a RAID6 using partition 1 of #8 2TB drives.Bear with me here; just trying to be complete and not waste your time.
Attempting to mount give this:[root]# mount -v /dev/md1 /asc/array1mount: unknown filesystem type 'ext4'Note: it does "fake" mount with ption (which apparently does everything except the system call):[root]# mount -f -v /dev/md1/dev/md1 on /asc/array1 type ext4 (rw,grpquota,usrquote)e2fsprogs:Package e2fsprogs-1.39-23.el5_5.1.x86_64 already installed and latest version (for Centos 5.6; CentOS 6x uses the 1.41...)
I have done a recent install of Debian squeeze on a laptop. I set up LVM with 3 LV's, one for the root filesystem, one for /home, and another for swap. I then used lvextend to increase the size of the LV's. This additional space is shown if I enter lvdisplay (shortened for clarity):
- Logical volume -
LV Name /dev/auriga/swap
LV Size 4.66 GiB
- Logical volume -
LV Name /dev/auriga/root
LV Size 15.97 GiB
- Logical volume -
LV Name /dev/auriga/home
LV Size 169.01 GiB
However, if I use df, it still shows the previous size.
/dev/mapper/auriga-root 14G 8.0G 5.2G 61% /
/dev/sda1 221M 16M 193M 8% /boot
/dev/mapper/auriga-home 147G 421M 139G 1% /home
I have even tried restarting as well. I do not understand why df would still show that /home is 147GB, when I extended it to 169GB using lvextend. Similarly for the root, which was extended by 2GB from 14GB to 16GB.
I was finally upgrading from F12 to F14, and as you'd expect from someone posting for the first time here, I did something stupid. My system has two drives set up as RAID-1 with LVM for the entirety of them. I added a new drive to use as the boot & OS drive, but during the install process I believe I somehow managed to wipe the LVM information from the RAIDed drives (though I did not install to them or format them).
While I have a working F14 install on the new drive, I would like to get access to the data I have on the RAID. However, the LVM tools show the RAID drives as uninitialized. If I try booting off the RAID, it gets partway through the bootup (the white part of the progress bar gets about halfway) before displaying "No root device found. Boot failed, sleeping forever." This occurs regardless of whether I have the new drive plugged in or not. I've been googling for the past several hours and haven't found anything that allows me to access the the volumes on the RAIDed drives.