[osol-discuss] how to mount linux partition
Hi, I am using opensolaris, ( in-preview ) uname -a gave SunOS opensolaris 5.11 snv_75 i86pc i386 i86pc Solaris Since I am new to solaris I have many questions, please some one can help me, thanks in advance This is the first one : I have opensolaris and linux ( debian 4.0 ) installed on my laptop, I want to mount linux partition from solaris. The disk is identified as (/dev/sda on linux, the linux partition I want to mount is sda3 ) /dev/dsk/c8t0d0 the format command gives: 0. c8t0d0 DEFAULT cyl 1997 alt 2 hd 255 sec 63 /[EMAIL PROTECTED],0/pci103c,[EMAIL PROTECTED],2/[EMAIL PROTECTED],0 what should be the mount command ? secondly: I have a problem to configure permanently the network card, When I use the ifconfig, it works, but if I put the address in the file /etc/hostname.rtls0 (rtls0 name of the module), it seems not be read, I don't get the address. The name of my machine is opensolaris, it is save in /etc/nodename. What is wrong here Thanks for help bela This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] how to mount linux partition
On Jan 9, 2008 6:09 AM, A.Belahcene [EMAIL PROTECTED] wrote: Hi, I am using opensolaris, ( in-preview ) uname -a gave SunOS opensolaris 5.11 snv_75 i86pc i386 i86pc Solaris Since I am new to solaris I have many questions, please some one can help me, thanks in advance This is the first one : I have opensolaris and linux ( debian 4.0 ) installed on my laptop, I want to mount linux partition from solaris. The disk is identified as (/dev/sda on linux, the linux partition I want to mount is sda3 ) /dev/dsk/c8t0d0 the format command gives: 0. c8t0d0 DEFAULT cyl 1997 alt 2 hd 255 sec 63 /[EMAIL PROTECTED],0/pci103c,[EMAIL PROTECTED],2/[EMAIL PROTECTED],0 what should be the mount command ? it would depend on the linux filesystem youre using, and you would still need software that is not included in indiana, check the belenix web page, i think the software to mount ext2 (and ext3) is there and all you can get is readonly access secondly: I have a problem to configure permanently the network card, When I use the ifconfig, it works, but if I put the address in the file /etc/hostname.rtls0 (rtls0 name of the module), it seems not be read, I don't get the address. The name of my machine is opensolaris, it is save in /etc/nodename. What is wrong here indiana uses nwam to configure the network, you need to disable svc:/network/physical:nwam and enable svc:/network/physical:default check man svcs and man svcadm nacho ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Kernel Panic with sfmmu_tsbmiss_exception+0x54() in stack trace
On Wed, 9 Jan 2008, Vamsee Priya wrote: Hi All, We have a kernel module called IPFS which lies in between VFS and UFS. We are getting a kernel panic (with the following stack trace) very frequently on ATCA blades where as the panic is almost rare on CPCI blades. Hi Vamsee, Are you willing to share the sourcecode for that driver ? Are you considering an OpenSolaris project for this ? Generically, filesystem filter drivers on Solaris are unsupported - you're doing something there that the filesystem framework is not designed to deal with. That doesn't mean it's impossible to do, but honestly, makes it difficult to advise if there are no sources to look into. Below, you're trying a VOP_READ() operation on a vnode bound to a fifo, and hence that ends in strread(); need the crashdump to tell you more about where exactly the invalid pointer comes from. Given that you say you're trying to interpose on top of UFS, that you end up attempting to read from a stream seems unexpected/undesired. Most likely you missed a VN_HOLD() where you first picked up a reference to that vnode, and later the vnode that at one point in time might've been UFS got released and reused (for a fifo not a file). As far as crashdump analysis on SPARC goes: There's an old book (now out of print but still available 2nd hand via e.g. Amazon), called Panic !. It's quite outdated regarding the dump analysis techniques but covers the SPARC architecture (assembly language, register windows) well enough. There are also courses on it - Max Bruning, who posts on mdb-discuss every now and then, for example, teaches a good one. Have you tried to talk to your local OpenSolaris users group (see the references on the website at http://opensolaris.org/os/community/advocacy/usergroups/ug-leaders/) ? It's possible to set something up, usually only a question of who covers the costs :) FrankH. sfmmu_tsbmiss_exception+0x54(2a1038555a0, 42001, 31, 0, d5b28, 6001e6d0800) ktl0+0x64(60008a47564, 42f98, 1, fff8, 1e5b76, 1) uiomove+0x90(60008a4755c, 8, 0, 2a103855950, 0, 8) struiocopyout+0x38(60008cf2fc0, 2a103855950, 2a103855864, 0, 60008a47564, 1) strread+0x4b4(0, 2a103855950, 0, 6001f93fd28, 0, 0) ipfs_in+0x1e8(0, 30022006540, 6001f93fd28, 8, 2a103855ab0, 0) ipfs_active_in+0xec(60005e8c000, 30022006540, 3001f1f5ec0, 60011bc6000, 0, 60005e8c0d8) thread_start+4(60005e8c000, 0, 0, 0, 0, 0). When can this sfmmu_tsbmiss_exception occur? Thanks in advance Regards, Priya -- No good can come from selling your freedom, not for all the gold in the world, for the value of this heavenly gift far exceeds that of any fortune on earth. -- ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] can I run solaris express
Just one more confirmation. Does community express version always the latest build, right? Thank you and sorry for my bad English. No problem, your English is great. The Community Edition is always the latest binary build of Solaris Express. Have fun! This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] can I run solaris express
Thank you This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] can I run solaris express
vuthecuong writes: Thanks for following my thread and reply my question. Now I'm downloading the community express ones. In fact, I already gave it a try about 6 months ago. Of course I knew that unlike linux that can be installed at extended partition, solaris must be installed in primary partition, That's currently correct ... I know there's a project working on this, but I don't know the status. Extended partitions are strange beasts. but right from first booting for installation, I remembered that after dialog (with red border) showing that it was extracting runtime JRE or something like that (I not remembered exactly), the installation hang forever :( That *sounds* like it might be a BIOS problem of some sort. I've seen reports of other platforms with problems like that in the past. If you run into similar problems (or, really, any problems), do post here, and someone with experience in that area will likely speak up with some suggestions. At that time I was too busy with other works so I gave up soon without asking forum about solution. What's a shame of my efforts :) Now I would like to give it a try again and post questions here if I have probs. Sounds good. The info that P5LD2 worked with opensolaris convinced me. Just one more confirmation. Does community express version always the latest build, right? Yes; that's the latest and greatest Nevada build from Sun. There are other distributions that are based on OpenSolaris, though, including Indiana (an experimental one from Sun), Nexenta (an independent GNU-flavored one), SchilliX, BeleniX, and MarTUX. Pointers are here: http://www.genunix.org/wiki/index.php/Distributions -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Solaris 10 08/07 fujitsu servers with ESF 3.0A20 metaset problem
Hi Every one, I would appreciate if you can look into the problem and get me a solution. I have applied the patch set for 10 Recommended from Fujitsu site as well you can see the error messages below. the following error messages was without ESF3.0 from fujitsu siemens. when i instaaled ESF 3.0 system panics when i ran # metaset -s wh_ds -t thanks Platform Fujitsu PW650 OS: Solaris 10 08/07 Metaset Creation steps #metaset –s wh_ds –a –h misys-wh #metaset –s wh_ds –a c8t0d2 c8t0d3 c8t0d4 c8t0d5 c8t0d6 c8t0d7 c8t0d8 c8t0d9 c8t0d10 Metaset Status after creation # metadb –s wh_ds flags first blk block count au 16 8192/dev/sd27h au 82088192/dev/sd27h au 16 8192/dev/sd26h au 82088192/dev/sd26h au 16 8192/dev/sd25h au 82088192/dev/sd25h au 16 8192/dev/sd24h au 82088192/dev/sd24h au 16 8192/dev/sd23h au 82088192/dev/sd23h au 16 8192/dev/sd22h au 82088192/dev/sd22h au 16 8192/dev/sd21h au 82088192/dev/sd21h au 16 8192/dev/sd20h au 82088192/dev/sd20h au 16 8192/dev/sd19h au 82088192/dev/sd19h #metaset Set name = wh_ds, Set number = 1 HostOwner misys-wh Yes Drive Dbase c8t0d2Yes c8t0d3Yes c8t0d4Yes c8t0d5Yes c8t0d6Yes c8t0d7Yes c8t0d8Yes c8t0d9Yes c8t0d10 Yes Metaset release and takeover operation #metaset –s wh_ds –r #metaset Set name = wh_ds, Set number = 1 HostOwner misys-wh Drive Dbase c8t0d2Yes c8t0d3Yes c8t0d4Yes c8t0d5Yes c8t0d6Yes c8t0d7Yes c8t0d8Yes c8t0d9Yes c8t0d10 Yes #metaset –s wh_ds -t metaset: misys-wh: wh_ds: there are no existing databases #tail -50 /var/adm/messages Jan 8 16:24:26 misys-wh last message repeated 1 time Jan 8 16:24:26 misys-wh genunix: [ID 472443 kern.warning] WARNING: dev_lclose: extra close of dev_t 0x2000bf from md`initit() Jan 8 16:24:26 misys-wh last message repeated 1 time Jan 8 16:24:26 misys-wh genunix: [ID 472443 kern.warning] WARNING: dev_lclose: extra close of dev_t 0x2000b7 from md`initit() Jan 8 16:24:26 misys-wh last message repeated 1 time Jan 8 16:24:26 misys-wh genunix: [ID 472443 kern.warning] WARNING: dev_lclose: extra close of dev_t 0x2000af from md`initit() Jan 8 16:24:26 misys-wh last message repeated 1 time Jan 8 16:24:26 misys-wh genunix: [ID 472443 kern.warning] WARNING: dev_lclose: extra close of dev_t 0x2000a7 from md`initit() Jan 8 16:24:26 misys-wh last message repeated 1 time Jan 8 16:24:26 misys-wh genunix: [ID 472443 kern.warning] WARNING: dev_lclose: extra close of dev_t 0x20009f from md`initit() This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Solaris 10 08/07 fujitsu servers with ESF 3.0A20 metaset problem
Hi Every one, I would appreciate if you can look into the problem and get me a solution. I have applied the patch set for 10 Recommended from Fujitsu site as well you can see the error messages below. the following error messages was without ESF3.0 from fujitsu siemens. when i instaaled ESF 3.0 system panics when i ran # metaset -s wh_ds -t thanks Platform Fujitsu PW650 OS: Solaris 10 08/07 Metaset Creation steps #metaset –s wh_ds –a –h misys-wh #metaset –s wh_ds –a c8t0d2 c8t0d3 c8t0d4 c8t0d5 c8t0d6 c8t0d7 c8t0d8 c8t0d9 c8t0d10 Metaset Status after creation # metadb –s wh_ds flags first blk block count au 16 8192/dev/sd27h au 82088192/dev/sd27h au 16 8192/dev/sd26h au 82088192/dev/sd26h au 16 8192/dev/sd25h au 82088192/dev/sd25h au 16 8192/dev/sd24h au 82088192/dev/sd24h au 16 8192/dev/sd23h au 82088192/dev/sd23h au 16 8192/dev/sd22h au 82088192/dev/sd22h au 16 8192/dev/sd21h au 82088192/dev/sd21h au 16 8192/dev/sd20h au 82088192/dev/sd20h au 16 8192/dev/sd19h au 82088192/dev/sd19h #metaset Set name = wh_ds, Set number = 1 HostOwner misys-wh Yes Drive Dbase c8t0d2Yes c8t0d3Yes c8t0d4Yes c8t0d5Yes c8t0d6Yes c8t0d7Yes c8t0d8Yes c8t0d9Yes c8t0d10 Yes Metaset release and takeover operation #metaset –s wh_ds –r #metaset Set name = wh_ds, Set number = 1 HostOwner misys-wh Drive Dbase c8t0d2Yes c8t0d3Yes c8t0d4Yes c8t0d5Yes c8t0d6Yes c8t0d7Yes c8t0d8Yes c8t0d9Yes c8t0d10 Yes #metaset –s wh_ds -t metaset: misys-wh: wh_ds: there are no existing databases #tail -50 /var/adm/messages Jan 8 16:24:26 misys-wh last message repeated 1 time Jan 8 16:24:26 misys-wh genunix: [ID 472443 kern.warning] WARNING: dev_lclose: extra close of dev_t 0x2000bf from md`initit() Jan 8 16:24:26 misys-wh last message repeated 1 time Jan 8 16:24:26 misys-wh genunix: [ID 472443 kern.warning] WARNING: dev_lclose: extra close of dev_t 0x2000b7 from md`initit() Jan 8 16:24:26 misys-wh last message repeated 1 time Jan 8 16:24:26 misys-wh genunix: [ID 472443 kern.warning] WARNING: dev_lclose: extra close of dev_t 0x2000af from md`initit() Jan 8 16:24:26 misys-wh last message repeated 1 time Jan 8 16:24:26 misys-wh genunix: [ID 472443 kern.warning] WARNING: dev_lclose: extra close of dev_t 0x2000a7 from md`initit() Jan 8 16:24:26 misys-wh last message repeated 1 time Jan 8 16:24:26 misys-wh genunix: [ID 472443 kern.warning] WARNING: dev_lclose: extra close of dev_t 0x20009f from md`initit() This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] can I run solaris express
Tnx u for reply. I'll go for opensolaris. I do hope it's compatible with my current hardware. -Original Message- From: James Carlson [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 09, 2008 8:59 PM To: Vu The Cuong Cc: opensolaris-discuss@opensolaris.org Subject: Re: [osol-discuss] can I run solaris express vuthecuong writes: Thanks for following my thread and reply my question. Now I'm downloading the community express ones. In fact, I already gave it a try about 6 months ago. Of course I knew that unlike linux that can be installed at extended partition, solaris must be installed in primary partition, That's currently correct ... I know there's a project working on this, but I don't know the status. Extended partitions are strange beasts. but right from first booting for installation, I remembered that after dialog (with red border) showing that it was extracting runtime JRE or something like that (I not remembered exactly), the installation hang forever :( That *sounds* like it might be a BIOS problem of some sort. I've seen reports of other platforms with problems like that in the past. If you run into similar problems (or, really, any problems), do post here, and someone with experience in that area will likely speak up with some suggestions. At that time I was too busy with other works so I gave up soon without asking forum about solution. What's a shame of my efforts :) Now I would like to give it a try again and post questions here if I have probs. Sounds good. The info that P5LD2 worked with opensolaris convinced me. Just one more confirmation. Does community express version always the latest build, right? Yes; that's the latest and greatest Nevada build from Sun. There are other distributions that are based on OpenSolaris, though, including Indiana (an experimental one from Sun), Nexenta (an independent GNU-flavored one), SchilliX, BeleniX, and MarTUX. Pointers are here: http://www.genunix.org/wiki/index.php/Distributions -- James Carlson, Solaris Networking [EMAIL PROTECTED] Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] DTrace normalize
profile:::tick-1sec
/this-cnt == 10/
{
normalize(@runq, 1);
printa([EMAIL PROTECTED], @runq);
exit(0);
}
The output is an integer, but I want a decimal, e.g. 7.4 instead of 7. How
could I do that?
Thanks
Victor
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Solaris 10 08/07 fujitsu servers with ESF 3.0A20 metaset problem
Janet, ESF 3.0 is the Fujitsu Extended Service Facility for Primepower servers. Its the Software that contains Fujitsu specific drivers and machine management tools for Primepower hosts. I reccommend that you contact Fujitsu for advice on this product. Its not a Product that has been opened Sourced and its not part of Opensolaris I have experienced that a metadb set of replicas was destroyed on a much smaller machine. A SUN V240 with 4 disks. Apperently it was a particular disc drive that had some firmware problem. It was resolved by only creating one meta db replica per disc. You seem to have two replicas per disc . //Lars This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
