On 10/19/10 7:57 AM, Andrew Williamson - Fujitsu wrote:
All
I did find one thing however (typically, AFTER hitting the send button... grrr)
:
0 unassigned wm 0 0 (0/0/0) 0
1 unassigned wm 0 0 (0/0/0) 0
2 backup wm 0 - 1845 64.90GB (1846/0/0) 136101888
Slice zero hadn't been set up and defining that to be the same as s2 (though in
that case why not just use s2 - was just following convention) made it work.
Newfs now complete.
>
However, I'm still curious about the geometry of d5 and why it's so different
to the others - can anyone advise please ?
With Solaris 10 Update 8, the default geometry for vdisk has been changed
because
it was not suitable for vdisks greater than 1TB. Also the new geometry make it
easier to grow a vdisk while preserving an existing partitioning (because we can
increase the number of cylinders without changing the number of heads and
cylinders).
alex.
-----Original Message-----
From: Andrew Williamson - Fujitsu
Sent: 19 October 2010 15:01
To: [email protected]
Subject: growing a backend disk file
Hi
Can anyone advise what's gone wrong here please ?
I had a test machine with a 60g backend (data.img below) on one of the disks. I needed it
to be 65g and the data in it can be re-cloned from the live system, so I thought,
"not a problem, stop the domain, remove the device, create a new backend, start the
domain, newfs, re-clone, be happy".
Fail.
It appears the LDOM is seeing the disk wrongly, check the parameters that
format reports below:
AVAILABLE DISK SELECTIONS:
0. c0d0<SUN-DiskImage-8GB cyl 27960 alt 2 hd 1 sec 600>
/virtual-devi...@100/channel-devi...@200/d...@0
1. c0d1<SUN-DiskImage-4GB cyl 13979 alt 2 hd 1 sec 600>
/virtual-devi...@100/channel-devi...@200/d...@1
2. c0d2<SUN-DiskImage-100MB cyl 339 alt 2 hd 1 sec 600>
/virtual-devi...@100/channel-devi...@200/d...@2
3. c0d3<SUN-DiskImage-1GB cyl 3493 alt 2 hd 1 sec 600>
/virtual-devi...@100/channel-devi...@200/d...@3
4. c0d4<SUN-DiskImage-10GB cyl 34950 alt 2 hd 1 sec 600>
/virtual-devi...@100/channel-devi...@200/d...@4
5. c0d5<SUN-DiskImage-65GB cyl 1846 alt 2 hd 96 sec 768>
/virtual-devi...@100/channel-devi...@200/d...@5
96 heads?? 768 sectors?? Cylinders is way too few!
6. c0d6<SUN-DiskImage-1GB cyl 3493 alt 2 hd 1 sec 600>
/virtual-devi...@100/channel-devi...@200/d...@6
7. c0d7<SUN-DiskImage-1GB cyl 3493 alt 2 hd 1 sec 600>
/virtual-devi...@100/channel-devi...@200/d...@7
8. c0d8<SUN-DiskImage-4GB cyl 13979 alt 2 hd 1 sec 600>
/virtual-devi...@100/channel-devi...@200/d...@8
Disk 5 is way wrong. Not even remotely working.
# newfs /dev/rdsk/c0d5s0
/dev/rdsk/c0d5s0: I/O error
I don't have a copy of what it should look like before the resize. The question
is, why has this happened, and what to do about it ?
Here's what I did to re-generate my larger file.
Before starting:
ldm ls -l primary
vdisk0 train-dom-r...@primary-vds0 0 d...@0 primary
vdisk1 train-dom-s...@primary-vds0 1 d...@1 primary
vdisk2 train-dom-us...@primary-vds0 2 d...@2 primary
vdisk3 train-dom-worksp...@primary-vds0 3 d...@3 primary
vdisk4 train-dom-ora...@primary-vds0 4 d...@4 primary
* vdisk5 train-dom-d...@primary-vds0 5 d...@5 primary
vdisk6 train-dom-l...@primary-vds0 6 d...@6 primary
vdisk7 train-dom-sp...@primary-vds0 7 d...@7 primary
vdisk8 train-dom-fi...@primary-vds0 8 d...@8 primary
ldm ls -l houtrain
NAME VOLUME OPTIONS MPGROUP DEVICE
primary-vds0 train-dom-root
/ldoms/houtrain/sys/root.img
train-dom-swap
/ldoms/houtrain/sys/swap.img
train-dom-users
/ldoms/houtrain/sys/users.img
train-dom-workspace
/ldoms/houtrain/sys/workspace.img
train-dom-oracle
/ldoms/houtrain/tpp/oracle.img
* train-dom-data
/ldoms/houtrain/dpp/data.img
train-dom-logs
/ldoms/houtrain/dpp/logs.img
train-dom-spool
/ldoms/houtrain/app/spool.img
train-dom-first
/ldoms/houtrain/app/first.img
bash-3.00# ldm remove-vdisk vdisk5 houtrain bash-3.00# ldm
remove-vdiskserverdevice train-dom-d...@primary-vds0 bash-3.00# rm data.img
bash-3.00# mkfile 65G data.img bash-3.00# ldm add-vdiskserverdevice
/ldoms/houtrain/dpp/data.img train-dom-d...@primary-vds0 bash-3.00# ldm
add-vdisk vdisk5 train-dom-d...@primary-vds0 houtrain
Started the domain, since then, I/O errors as above, system drops into single-user coz it
can't fsckall. That's not a problem in itself, I'm just wondering how come the system
things this "new" disk is so different to all the others ??
/dev/rdsk/c0d2s0 is clean
/dev/rdsk/c0d3s0 is clean
/dev/rdsk/c0d4s0 is clean
/dev/rdsk/c0d7s0 is clean
/dev/rdsk/c0d8s0 is clean
checking ufs filesystems
Can't open /dev/rdsk/c0d5s0: I/O error
/dev/rdsk/c0d5s0: CAN'T CHECK FILE SYSTEM.
/dev/rdsk/c0d5s0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
fsckall failed with exit code 1.
How to fix this, but more importantly what went wrong ??
xxx_sc> showhost
Sun System Firmware 7.2.10 2010/07/19 17:13
Host flash versions:
Hypervisor 1.7.9 2010/07/19 15:51
OBP 4.30.9 2010/07/16 09:01
POST 4.30.9 2010/07/16 09:39
Thanks
AW
______________________________________________
This email has been scanned by Netintelligence
http://www.netintelligence.com/email
_______________________________________________
ldoms-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
_______________________________________________
ldoms-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
