Increase root filesystem in ldom

Hi
I have a ldom having a flat file /ldoms/ldom1-data in the backend used as a virtual disk c0d2s0 for data In the ldom .Now this virtual disk is running out of space in the ldom How can I increase the size of this filesystem in the ldom or my only option is to create another file of bigger size in the primary domian ,export it to the ldom as a new Virtual disk ,parttion it in the ldom and copy the data from the old disk to the new
Appreciate any inputs
TIA

Hello
I don't think you can do with sol10u6 without any patch, assuming that you don't have SVM just and slice
Solaris Does Not Automatically Handle an Increase in LUN Size (Doc ID 1382180.1)
How to expand a UFS Lun in Solaris 10 (Doc ID 1451858.1)
And the previous doc I gave you has the example for ufs too but with sol11, so mixing a bit all this docs I think you will be able to do, but first don't forget to do a backup just in case something goes wrong.
How to Increase the Size of a Vdisk and Filesystem on a LDom Guest Domain (Doc ID 1549604.1)
—snip —
Procedure to increase size of a UFS filesystem based on SMI label in a guest domain running Solaris 11
Another way, is add a new LUN and do a mirror to a bigger LUN then remove the small LUN. (for this you need SVM or ZFS in the guest)
Regards
Eze

Similar Messages

Increase root filesystem size with VxVM

Hi All,
Can i increase the root fileystem size in solaris 10 after encapsulating the root disk into VxVM.
Thanks
---MGP---

I wouldn't try it.
If you have a mirror, I'd drop the mirror, copy everything over to the mirror disk (in normal, contiguous slices), then redo the VxVM encapsulation.
Root filesystem cannot be discontiguous, no concats, stripes, raid5s, only mirror. So growing is difficult unless the space is already past the end.
Easier to copy to another disk, reset the bits (/etc/system, /etc/vfstab), then boot from it.
Darren

Increase root partition on ufs filesystem

Hello
we have a virtual solaris vm with ufs the disk has become to small..
we have increased the vmfs but we are having problems increasing the filesystem as format only sees the old size.. fdisk does not seem to offer the possibility to expand the partition to its maximum size.. is it possible to change the label of a solaris partition so that it takes into account all the space that is available for it?
why fdisk does not see there is unallocated space.. i could create a second partition and mount it to other directory perhaps.
thank you.

Hi.
Solaris on X86 system placed on special general dos partittion.
fdisk - used for first level. On this level you can create one ( and only one) partition with type Solaris
and can create some additional partitions for other OS.
format - used for second level. It create additional partittions on solaris's partitions on first level. This label also store original size of disk.
So you need:
1. Increase Solaris partition on first level, using fdisk
2. Check that format detect new size of disk and increase/create new.
In case mistake on any steps - you lost data.
This problem correspond only for root fs and UFS.
On my choice - create addtional virtual disk and just add it to system.
For new disk use gpt (efi) type of label.
Regards.

[LVM] Shrinking /home to increase /root failed [solved]

Hi there,
Before doing anything wrong and risking data loss, I will better ask for your advice. I used the following commands to shrink my /home partition in order to increase /root:
# vgchange -a y
# e2fsck -f /dev/VolGroup00/Home
# resize2fs /dev/VolGroup00/Home 205G
# lvreduce -L 206G VolGroup00/Home
# lvextend -l +100%FREE VolGroup00/Arch
# e2fsck -f /dev/VolGroup00/Arch
# resize2fs /dev/VolGroup00/Arch
The initial size of the logical volume Home was 208GB according to lvdisplay. The volume Arch corresponds to my /root.
All commands completed successfully. However, on boot I get the following error:
Home: The filesystem size (according to the superblock) is 54525952 blocks
The physical size of the device is 54001664 blocks
Either the superblock or the partition table is likely to be corrupt!
Home: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY
I booted from a live disk and tried to run fsck manually. But it aborts with the same error.
What am I advised to do now?
Thanks!
Last edited by orschiro (2014-05-26 06:55:30)

Filesystems don't like it when parts of their storage go missing. You have to get the missing parts back.
Find your LVM backups / archives ( /etc/lvm/archive ), see if there is a file that says "created *before* lvreduce -L 206G VolGroup00/Home". That file would tell you where the /home partition was allocated before you shrank it.
You can use vgcfgrestore to get back to that state of things. At that point your /home should be accessible again - or at least fsckable. (But of course the /root is broke then - can't have both).
1) Before doing anything else, make a backup of your /root files if you need one
2) Free some space so you can use snapshot before you fsck. If fsck messes up you really are in trouble.
The real interesting question is what went wrong with the shrink in the first place. Your commands look like they should have worked. Most likely the resize2fs failed somehow? since it still believes itself to be 208GiB large.
Last edited by frostschutz (2014-05-22 15:38:19)

Regarding increasing root file system size

Hi folks,
I need urgent help regarding increasing the rool file system size from 40gb to 72 gb by decreasing swap from 64gb to 32gb with out any loss.
please find the current partiton config:
Part Tag Flag Cylinders Size Blocks
0 root wm 6595 - 10787 40.69GB (4193/0/0) 85335936
1 swap wm 2 - 6594 64.00GB (6595/0/0) 134221440
2 backup wm 0 - 14086 136.71GB (14087/0/0) 286698624
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 10788 - 14050 32.01GB (3298/0/0) 67120896
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
i need to change this like below.
Part Tag Flag Cylinders Size Blocks
0 root wm 3299 - 10787 72.69GB (4193/0/0) 152446656
1 swap wm 2 - 3298 32.00GB (3298/0/0) 67110720
2 backup wm 0 - 14086 136.71GB (14087/0/0) 286698624
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 10788 - 14086 32.01GB (3298/0/0) 67120896
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
kin dlyhelp me on this....
Thanks in advance,
Prathap

Sorry, can't be done.
If it was any other filesystem than root, you could do by using SVM.
But root filesystems can't be stripes or concats. Only simple mirrors.
So SVM isnt going to work.
If the spare space was after the partiton. You might have been able to do it by the "dirty" method of manually expanding the partition and using
growfs to expand it. You would have had to do it by netbooting or cd booting since growfs can't be used on the current root.
But in any case, you can't do that either since the space if before the partition not after it.
So, reinstalling is your only option..
Well, If you have a spare disk, you might be able to copy the filesystem over to a larger partition on the other disk, growfs it and boot off that instead.
You'd want to try it on a test systen first...

CentOS based linux VM running on Hyper-v : Checking root filesystem fails when kernel switches having old PV(para virtualised driver based on 2.6.32 linux kernel) to new PV(which is equivalent to linux integration component 3.4)

hi all,
I am running a CentOS base VM on top of Hyper-V server. I upgraded PV drivers of Hyper-V in linux kernel 2.6.32 in order to support
Windows Server 2012, then i am hitting below issue on Windows Server 2008 when kernel switches from old PV(which is 2.6.32 based) to new PV(which is equivalent to linux integration component 3.4).i
am hitting following filesystem check error messages :
Setting hostname hostname:
Checking root filesystem
fsck.ext3/dev/hda2:
The superblock could not be read or does not describe correct ext2 filesystem. If the device is valid and it really contains an ext2
filesystem(and not swap or ufs or something else),then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
: No such file or directory while trying to open /dev/hda2
*** An error occurred during the filesystem check.
*** Dropping you to a shell; the system will reboot
*** When you leave the shell.
Also, when I go to the repair filesystem mode. I found out the strange behaviour when i ran those command :
(Repair filesytem) 1 # mount
/dev/hda2 on / type ext3 (rw)
proc on /proc type proc (rw)
(Repair filesystem) 1# cat /etc/mtab
/dev/hda2 /ext3 rw 0 0
proc /proc proc rw 0 0
(Repair filesystem) 1# df
Filesystem 1K-blocks used Available Use% Mountedon
/dev/hda2 4%
I think for all above command there should be /dev/sda2 instead of /dev/hda2.
Also my fstab , and fdisk -l looks like ok for me.
(Repair filesystem) 1# cat /etc/fstab
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
LABEL=swap-xvda3 swap swap defults 0 0
(Repair filesystem) 1# fdisk -l
Device Boot Start End Block Id System
/dev/sda1 * 1 49 98535 83 Linux
Partition 1 does not end with cylinder boundary.
/dev/sda2 49 19197 39062500 83 Linux
Partition 2 does not end with cylinder boundary.
/dev/sda3 ......
Partition 3 does not ......
/dev/sda4 ......
Partition 4 does not end ....
(Repair filesystem) 1# e2label /dev/sda1
/boot
(Repair filesystem) 1# e2label /dev/sda2
(Repair fielsystem) 1# ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4
(Repair filesyatem) 1# ls /dev/hd*
ls: /dev/hd*: No such file or directory
Kindly suggest any configuration of windows server or kernel configs missing or how to resolve this issues
Many many thanks for your reply.
thanks & Regards,
Ujjwal

i am not able to understand duplicate UUID and from where it is picking /dev/hda* ?
~
VVM:>>
VVM:>> Output of dmesg | grep ata contain substring "Hyper-V" ?
VVM:>>
it doesn't contain "Hyper-V" or ata related message and the output doesn't change with boot parameter reserve=0x1f0, 0x8
~~
~~~~
==
output of dmesg related "ata" Ubuntu v13.04 mini.iso ( with boot parameter reserve=0x1f0, 0x8)
==
see later ( in "good situation" example )
~~
===
Disable legacy ATA driver by adding the following to kernel command line in /boot/grub/menu.lst:
reserve=0x1f0, 0x8
. (This option reserves this I/O region and prevents ata_piix from loading).
==
See output of dmesg related "ata" Ubuntu v13.04 mini.iso ( with boot parameter reserve=0x1f0, 0x8) :
~~
[ 0.176027]
libata version 3.00 loaded.
[ 0.713319]
ata_piix 0000:00:07.1: version 2.13
[ 0.713397]
ata_piix 0000:00:07.1: device not available (can't reserve [io 0x0000-0x0007])
[ 0.713404]
ata_piix: probe of 0000:00:07.1 failed with error -22
[ 0.713474]
pata_acpi 0000:00:07.1: device not available (can't reserve [io 0x0000-0x0007])
[ 0.713479]
pata_acpi: probe of 0000:00:07.1 failed with error -22
~~
As result: 1) IDE disk handled by hv_storvsc , but 2) no CD-ROM device
==
~ # blkid
/dev/sda1: LABEL="ARCH_BOOT" UUID="009c2043-4bl7-4f95-al4d-fb8951f95b5d" TYPE="ext2"
==
~~
VVM>>
VVM>>Q1: Output of blkid contain duplicate UUID ?
VVM>>
-> blkid contains duplicate UUID, below are the output.
~~
This situation is classic problem "
use hv_storvsc instead of ata_piix to handle the IDE disks devices ( but not for the DVD-ROM / CD-ROM device handling)
~~
For compare, see example "good situation":
See output of dmesg related "ata" Ubuntu v13.04 mini.iso ( without boot parameter reserve=0x1f0, 0x8) :
~~~~
~ # dmesg |grep ata
[ 0.167224] libata version 3.00 loaded.
[ 0.703109] ata_piix 0000:00:07.1: version 2.13
[ 0.703267] ata_piix 0000:00:07.1: Hyper-V Virtual Machine detected, ATA device ignore set
[ 0.703339] ata_piix 0000:00:07.1: setting latency timer to 64
[ 0.704968] scsi0 : ata_piix
[ 0.705713] scsi1 : ata_piix
[ 0.706191] atal: PATA max UDMA/33 cmd 0xlf0 ctl 0x3f6 bmdma 0xffa0 irq 14
[ 0.706194] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
[ 0.868844] atal.00: host indicates ignore ATA devices, ignored
[ 0.869142] ata2.00: ATAPI: Virtual CD, , max MWDMA2
[ 0.871736] ata2.00: configured for MWDMA2
~~~~
===
~ # uname -a
Linux ubuntu 3.7.0-7-generic #15-Ubuntu SUP Sat Dec 15 14:13:08 UTC 2012 x86_64 GNU/Linux
~ # lsmod
hv_netvsc 22769 0
hv_storvsc 17496 3
hv_utils 13569 0
hv_vmbus 34432 3 hv_netvsc,hv_storvsc,hv_utils
~ # blkid
/dev/sr0: LABEL=”CDROM" TYPE="iso9660”
/dev/sda1: LABEL="ARCH_BOOT" UUID="009c2043-4bl7-4f95-al4d-fb8951f95b5d" TYPE="ext2"
===
( only CD-ROM and 1( one) IDE disk connected to ATA)
~~
regarding ata_piix.c patch . . .
As far as i understand this patch , it ignore ATA devices on Hyper-V when PV drivers(CONFIG_HYPERV_STORAGE=y) are enabled.
~~
Yes:
ignore ATA-HDD ( but not ignore ATA CD-ROM ) on Hyper-V when PV drivers(CONFIG_HYPERV_STORAGE=y) are enabled.
~
this patches need be backported:
cd006086fa5d ata_piix: defer disks to the Hyper-V drivers by default
and its prerequisite
db63a4c8115a libata: add a host flag to ignore detected ATA devices
~
~~
P.S.
Are You do this:
==
As temporary solution, increase on 1-2 Gb size all .vhd connected to IDE bus
( but not increase size of partitions inside disks)
==
? fsck write message a-la: "no error in file system" ?
2013-01-24 Answer by Ujjwal Kumar: As a temporary solution looks ok for me, but [ VVM: need true solution ]
P.P.S.
To Ujjwal Kumar :
My e-mail:
ZZZZZZZZZZZZZZZ
please send e-mail to me, in reply I send to You patches to ata_piix ( and *.c before and after patches) , etc.
} on 2013-01-14 -- DoNe

Root filesystem

Can someone give me a best practice for increasing the root filesystem?

replayed wrote:
I did something stupid and screwed up the permissions in /Library and /Applications.
Long story short: I wanted to backup those directories before sending my MBP in for repairs. Rather than take the time to figure out Time Machine as an old Unix hand and newcomer to Mac OS X, I chose to use tar and cpio to backup those files from / that had been modified since my last OS install. Rookie mistake.
Having copied back those files and directories onto their former location, cpio lost all owner and group info, with everything winding up with owner root and group admin. Basic access permissions look preserved, but ACL info is presumably gone as well.
Surprisingly, my computer seems fine for the most part. A few applications complained about extensions, and I managed to quiet them by chgrp'ing a few .kext directories back to wheel.
But my latest software updates -- Safari 4.0.4 and Security Update 2009-006 -- are aborting while complaining about access issues with /.
I fired up Disk Utility and tried to Verify Disk Permissions, but the attempt fails immediately after announcing "Reading permissions database" with the error "The underlying task reported failure on exit."
I'm hoping to avoid a complete reinstall (of course), and I'm thinking I might get out of jail free if I can just manage to restore the correct ownership and permissions to the /Library/Receipts directory, which I understand is where canonical permissions are archived.
Am I on the right track here? Is there anything else I can do to restore permissions short of a full reinstall?
Any advice or suggestions would be appreciated.
honestly, I would reinstall in this situation. the permissions are too messed up at this point. that will be much quicker than anything else. an archive and install on top of your current system should fix things up.

[SOLVED] df -h does not reflect true root filesystem size

Why does df -h show root filesystem as being only 20G?
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/cryptroot 20G 15G 4.6G 76% /
dev 7.7G 0 7.7G 0% /dev
run 7.7G 668K 7.7G 1% /run
tmpfs 7.7G 70M 7.7G 1% /dev/shm
tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
tmpfs 7.7G 224K 7.7G 1% /tmp
/dev/sda1 239M 40M 183M 18% /boot
tmpfs 1.6G 8.0K 1.6G 1% /run/user/1000
That is what my df -h output looks like. My setup is full disk encryption using dm-crypt with LUKS, per the guide on arch wiki. I basically created one /boot partition and left the rest of the disk to be an encrypted partition for the root filesystem. So why is my system complaining about (and acting as if it's running out of space)? Have I forgotten something?
Thank you for reading this. Let me know if you need any more logs or info on my setup - I realise I haven't provided very much info here, but I can't think of what to provide.
Last edited by domentoi (2014-12-24 19:02:32)

This is lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 250M 0 part /boot
└─sda2 8:2 0 465.5G 0 part
└─cryptroot 254:0 0 465.5G 0 crypt /
sdb 8:16 0 14.9G 0 disk
└─sdb1 8:17 0 14.9G 0 part
and fdisk -l
Disk /dev/sdb: 14.9 GiB, 16013942784 bytes, 31277232 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5da5572f
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 31275007 31272960 14.9G 73 unknown
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xa5018820
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 514047 512000 250M 83 Linux
/dev/sda2 514048 976773167 976259120 465.5G 83 Linux
Disk /dev/mapper/cryptroot: 465.5 GiB, 499842572288 bytes, 976255024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdc: 1.4 TiB, 1500301908480 bytes, 2930277165 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x445e51a8
And graysky: I thought I made the partition for /boot 250 MB and the encrypted partition 465.5 GB but I'm now quite sure I did something wrong...
Thank you all

After upgrading to Solaris 10 "Can't load the root filesystem" on V245

I have a Sunfire V245 that was running on Solaris 9 (very stable). I upgraded to Solaris 10 (6/06) this morning and everything seemed to go smoothly. After the upgrade the system rebooted, but will not boot. I get the following uptput;
Rebooting with command: boot
Boot device: disk File and args:
SunOS Release 5.10 Version Generic_118833-17 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
pxb_bcm: cannot load driver
Cannot load drivers for /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk@0,0:a
Can't load the root filesystem
Type 'go' to resume
"go" attempts to reboot, but I end up back in the same place.
Please help.
Thanks in advanced,
Craig

It seems like the driver for that device does not exist. Since the system installed successfully it means that it S10 did find a disk. I wonder if that was a different disk than the default disk. Please boot to the miniroot and check the disk info.

Moving root filesystem to another hard drive

Hi everyone,
I've been using Arch Linux for a few months now and it is by far my favorite Linux distribution.
I currently have Arch on an old Pentium III, with a whopping 20 GB IDE hard drive.
I'm building a new computer, and want to use a larger 160 GB SATA hard drive, and I was wondering what is the best way that I can just transfer my entire root filesystem so I don't have to bother copying all the scripts, programs, etc.
Can I just tarball my root directory, partition my new hard drive, and use some other LiveCD to copy the root partition? I know this shouldn't be that difficult, because everything in the root partition is in /, unlike Windows, which has association problems with the registry.
Thanks!

I'd never want to lead anyone down the garden path without at least trying this myself so for the last hour or so I've done just as described above on an old computer I have that I play around with and a spare small 8 gb hard drive. I first tried copying the files over with thunar but that didn't work too well (froze up) probably due to trying to copy /sys and /proc--duh.
I tried again using midnight commander (to install do #pacman -S mc) and it worked perfectly. The /dev directory copied over just fine but don't try copying /proc and /sys. Just make empty directories so the system can put what it needs there. Also just make an empty /mnt directory and put your devices in later--otherwise I'm not sure what would happen if you were copying your /mnt/newroot to itself, but I'm sure it wouldn't be good.
I tried to just install grub on the slave with #grub-install /dev/sdb and it said it installed fine but when I switched the slave to master and disconnected the old master, grub wouldn't boot (probably because it was installed to /dev/sdb?) so I had to use the arch install disk to install grub. Then, much to my surprise--like I had any doubts--I rebooted and now I'm posting this with the newly copied Arch with xfce4.
It might not be a bad idea to backup any really important stuff but you are just copying and unless you do something silly, everything should work fine.
Last edited by bgc1954 (2008-03-11 23:13:58)

Kinit mounts root filesystem as read only [HELP][solved]

hello
I've being messing around with my mkinitcpio trying to optimize my boot speed, i removed some of the hooks at the beginning i couldn't boot, but then now i can boot but the root filesystem mounts as read only, i tried everything my fstab looks fine, / exists with defaults i tried to mount it referencing by it's uuid or by it's name and i get the same results, it mounts the filesystem as root only all the time no mather what i do.
There is not logs since i started playing with mkinitcpio, or anything i searched everywhere in this forum and around the internet, and i can't find any solution that would work, i restored all the hooks and modules on mkinitcpio and the result it's still the same. i also changed the menu.lst in grub to vga=773 but that's about it.
Can anyone help with this please i can't seem to boot properly.
Regards
Last edited by ricardoduarte (2008-09-14 16:16:25)

Hello
Basically what happens it's that it loads all the uDev events then the loopback, it mounts the root read only, then when it checks filesystems it says
/dev/sda4: clean, 205184/481440 files, 1139604/1920356 blocks [fail]
************FILESYSTEM CHECK FAILED****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write: mount -n -o remount,rw / *
* When you exit the maintenance shell the will *
* reboot automatically. *
Now what bugs me its that i can do that mount -n -o remount,rw / with no problems and when i do
e2fsck -f /dev/sda4
it doesn't return any errors just says that 0.9 non continuous.
none of this makes sense to me!! thats why i though that the problem could be coming from mkinitcpio or something
any ideas
Thanks for your help, btw thanks for the quick reply
Regards
Last edited by ricardoduarte (2008-09-14 15:48:49)

ZFS root filesystem & slice 7 for metadb (SUNWjet)

Hi,
I'm planning to use ZFS root filesystem in Sun Cluster 3.3 environment, as written in documentation when we will use UFS share diskset then we need to create small slice for metadb on slice 7. In standar installation we can't create slice 7 when we install solaris with zfs root, then we can create it with jumpstart profile below :
# example Jumpstart profile -- ZFS with
# space on s7 left out of the zpool for SVM metadb
install_type initial_install
cluster SUNWCXall
filesys c0t0d0s7 32
pool rpool auto 2G 2G c0t0d0s0
so, my question is : "when we use SUNWjet (JumpStart(tm) Enterprise Toolkit) how we can write the profile similar to above jumpstart profile"?
Thanks very much, for your best answer.

This can be done with JET
You create the template as normal.
Then create a profile file with the slice 7 line.
Then edit the template to use it.
see
---8<
# It is also possible to append additional profile information to the JET
# derived one. Do this using the base_config_profile_append variable, but
# don't forget to fill out the remaining base_config_profile variables.
base_config_profile=""
base_config_profile_append="
---8<
It is how OpsCentre (which uses JET) does it.
JET questions are best asked on the external JET alias at yahoogorups (until the forum is setup on OTN)

[Solved] NFS shares root filesystem

[edit] Sorry, my fault. I was using Nautilus m(
and i think it silently switiched to using sftp.... still wondering why no password was prompted.
Hi!
I set up nfs following the wiki. It works, but i can access the whole remote-root-filesystem, not just the nfs-root. Is https://wiki.archlinux.org/index.php/NFS up to date?
greetings
Server:
cat /etc/exports
/srv/nfs4/ 192.168.0.0/24(ro,fsid=0,no_subtree_check)
/srv/nfs4/a 192.168.0.0/24(ro,no_subtree_check)
/srv/nfs4/b 192.168.0.0/24(ro,no_subtree_check)
[root@alarmpi srv]#
Client:
showmount -e 192.168.0.116
Export list for 192.168.0.116:
/srv/nfs4/a 192.168.0.0/24
/srv/nfs4/b 192.168.0.0/24
/srv/nfs4 192.168.0.0/24
Last edited by matto (2015-03-22 14:50:59)

Thanks for the hints. Meanwhile, I have done some more background reading on running Arch in VMWare Player. In particular I followed the guidelines in this article. So it turns out that X requires some special configuration when run from within VMWare.
pacman -S xf86-input-vmmouse xf86-video-vmware xf86-video-vesa svga-dri
and a vmwgfx module is supposed to be loaded. I installed tha packages and tried to load vmwgfx, but when I do lsmod I just can't see it. Then it was pointed out to me that it might be a kernel mismatch problem. The linux installed on nfsroot is 3.6.2 whereas for some reason uname -a gives me version 3.5.6.
I've tried to rebuild initramfs with the new kernel using -k switch of mkinicpio, but it didn't help. It still boots into 3.5.6. It as if the initramfs from the client was taking precedence. So then I went back to the previous image of my VM, updated the system, made appropriate changes to mkinitcpio.conf and run mkinitcpio... and it no longer boots. mount: protocol not supported. I will post the details in my other topic.

"ludowngrade" - Sol 8 root filesystem trashed after mounting on Sol 10?

I've been giving liveupgrade a shot and it seems to work well for upgrading Sol 8 to Sol 10 until a downgrade / rollback is attempted.
To make a long story short, luactivating back to the old Sol 8 instance doesn't work because I haven't figured out a way to completely unencapsulate the Sol 8 SVM root metadevice without completely removing all SVM metadevices and metadbs from the system before the luupgrade, and we can only reboot once, to activate the newupgrade.
This leaves the old Sol 8 root filesystem metadevice around after the upgrade (even though it is not mounted anywhere). After an luactivate back to the Sol 8 instance, something gets set wrong and the 5.8 kernel panics with all kinds of undefined symbol errors.
Which leaves me no choice but to reboot in Solaris 10, and mount the old Solaris 8 filesystem, then edit the Sol 8 /etc/system and vfstab files to boot off a plain, non-SVM root filesystem.
Here's the problem: Once I have mounted the Old Sol 8 filesystem in Sol 10, it fails fsck when booting Sol 8;
/dev/rdsk/c1t0d0s0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
# fsck /dev/rdsk/c1t0d0s0
BAD SUPERBLOCK AT BLOCK 16: BAD VALUES IN SUPER BLOCK
LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS? y
USE ALTERNATE SUPERBLOCK? y
FOUND ALTERNATE SUPERBLOCK AT 32 USING MKFS
CANCEL FILESYSTEM CHECK? n
Fortunately, recovering the alternate superblock makes the filesystem usable in Sol 8 again. Is this supposed to happen?
The only thing I can think of is I have logging enabled on the root FS in Sol 10, so apparently logging trashes the superblock in Sol 10 such that the FS cannot be mounted in Sol 8 without repair.
Better yet would be a HOWTO on how to luupgrade a root filesystem encapsulated in SVM without removing the metadevices first. It seems impossible since without any fiddling, all the LU instances on the host will share the SVM metadb's on the system, which leads to problems.

Did you upgrade the version of powerpath to a release supported on Solaris 10?

XFS Root Filesystem on LVM Stripe - Corruption

I want to create a LVM Stripe across two SATA drives. The problem I keep running into is, on boot, arch reports that a fsck needs to be run on the root filesystem, so it mounts it read only and allows me to type in the root password to get shell access. This all happens after I do the initial arch install, reboot, log in normally, do a pacman -Syu, reboot.
Here's what I have and what I did...
I have two 320G SATA Drives plugged into my system board (an ABIT AN-M2HD). My Bios is set to "AHCI Linux" for the SATA mode.
Boot the latest Arch CD install at command prompt:
cfdisk /dev/sda
create 125M Partition (for /boot) /dev/sda1
create 319G Partition /dev/sda2
cfdisk /dev/sdb
create 320G Partition /dev/sdb1
lvm pvcreate /dev/sda2 /dev/sdb1
lvm vgcreate lvmgrp0 /dev/sda2 /dev/sdb1
lvm lvcreate -i2 -I4 -L1G -nswap lvmgrp0
lvm lvcreate -i2 -I4 -L594G -nroot lvmgrp0
/arch/setup (I'm going to abbreviate this)
Hard Drive Setup (chose option 3)
Set swap to swap LV
Set root to root LV (xfs)
Set /dev/sda1 to /boot (ext3)
/etc/rc.conf USE LVM="YES"
Kerel Params = Boot from LVM Support? I answer Yes
Grub Looks Good.
Everything seemingly installs fine, I can reboot and arch comes right up. But after I do pacman -Syu everything goes to pot.
I suspect I have something wrong in alignment between the LVM stripe and XFS, but dont know..
alternately, should I set my LVM Stripe Size to a value larger than 4? I thought since on i686 max XFS block size is 4096 (4K) then they should match. Any thoughts on this?
help! ;-)
Ether..

I just wanted to add an update. It wasn't a LVM issue, it was a XFS issue.
I went to Arch 64 bit for a while and everything (above) worked just fine.. The usability and Lib32 issues with 64 bit lost it's luster and last weekend I went back to 32 bit Arch.
In going back to 32 bit I followed my procedure above for partitioning just as I had with the 64 bit version and after rebooting from the install and updating packman, the same thing occurred, the file system would start to corrupt, pacman would complain that libraries were truncated and so forth. After reboot, the /root partition would not mount read/write because it was not clean...
I reinstalled Arch 32 bit 6 times on Saturday trying various things in a scientific way and came to this conclusion:
__and I have no idea why__, but when I use the XFS file system on an install with Arch 32 bit, it hoses up. "Your Crazy" you might say, but trust me I've tried it different ways more than a dozen times. (I'm no n00b either, I've been an RHCE since 2003 and a daily Linux user since 1999.) Seems crazy, but XFS was a constant in all of my testing. The only thing I can figure is that it's my hardware and that's just a guess. 64 bit worked without a hitch with XFS. I even got desperate and installed / on a lone 60 gig partition (/dev/sda1) completely deleting all LVMs and it still corrupted with XFS and 32 bit
The Solution?
I used JFS. I have created the LVM Stripe as I have described above and it works great. No issues.
Weird..
For the sake of knowledge I have a:
AMD 5000+ Black Edition CPU
Abit AN-M2HD Motherboard
2 Gig Dual Channel RAM (2x1Gb)
2 320 Gig SATA Drive
1 SATA DVD Writer
-Ether..
Last edited by EtherNut (2008-01-29 14:54:01)

Increase root filesystem in ldom

Similar Messages

Maybe you are looking for