Re: problem using drive linking feature ...
Steve Dobbelstein <[email protected]> Thu, 18 Dec 2008 17:06:46 -0600
| Newsgroups | gmane.linux.evms.devel |
|---|---|
| Message-ID | <OF6014A68C.D78573C4-ON86257523.007E736A-86257523.007EFC8C@us.ibm.com> |
--===============5429659855546639931== Content-type: multipart/alternative; Boundary="0__=09BBFFB0DFEDF5FA8f9e8a93df938690918c09BBFFB0DFEDF5FA" Content-Disposition: inline --0__=09BBFFB0DFEDF5FA8f9e8a93df938690918c09BBFFB0DFEDF5FA Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable raespi <[email protected]> wrote on 12/18/2008 01:11:04 PM: > Thanks for answering ... I'm trying to put an Ext2/Ext3 filesystem ..= . I > tried putting a Fat filesystem but get the same error > > Thanks ... > > On Thu, 2008-12-18 at 11:14 -0600, Steve Dobbelstein wrote: > > raespi <[email protected]> wrote on 12/17/2008 05:20:09 AM:= > > > > > Hi, I have been using evms and I noticed a feature called drive > > linkin > > > only available to EVMS Volumes. I followed the guide down to the= > > rule. > > > I created 3 segments and later I created a Feature Object. I > > selected > > > Drive Link, i chose my three partitions from 3 different hdd's. > > Later I > > > created a EVMS volume out of that. The problem I had started whe= n I > > > tried to format the partition, something like: > > > > > > FSIM Plug-in NSSFS returned error code 1 when called to mkfs on > > > volume /dev/evms/homes > > > > > > Can anyone help me?? > > > > > > Thanks .... > > > > What file system were you trying to put on the volume? EVMS does n= ot > > ship support for an NSSFS file system. What happens if you try to = put > > a different file system on the volume? > > > > Steve D. Try running the mkfs from a command line outside of EVMS, e.g., "mke2fs /dev/evms/home" and see if it gives you any informative error messages. You might also take a look at the EVMS log, /var/log/evms-engine.log, and see if there are any helpful message= s. First search for "commit_changes" to get to the part where EVMS is appl= ying the changes. Then search for "mkfs". You can also try running with th= e debug level set to "debug" to put more detailed messaged into the log. = For example, run "evmsgui -d debug". Steve D.= --0__=09BBFFB0DFEDF5FA8f9e8a93df938690918c09BBFFB0DFEDF5FA Content-type: text/html; charset=US-ASCII Content-Disposition: inline Content-transfer-encoding: quoted-printable <html><body> <p><tt>raespi <[email protected]> wrote on 12/18/2008 01:= 11:04 PM:<br> <br> > Thanks for answering ... I'm trying to put an Ext2/Ext3 filesystem= ... I<br> > tried putting a Fat filesystem but get the same error<br> > <br> > Thanks ...<br> > <br> > On Thu, 2008-12-18 at 11:14 -0600, Steve Dobbelstein wrote:<br> > > raespi <[email protected]> wrote on 12/17/2008 = 05:20:09 AM:<br> > > <br> > > > Hi, I have been using evms and I noticed a feature calle= d drive<br> > > linkin<br> > > > only available to EVMS Volumes. I followed the gui= de down to the<br> > > rule.<br> > > > I created 3 segments and later I created a Feature= Object. I<br> > > selected<br> > > > Drive Link, i chose my three partitions from 3 different= hdd's.<br> > > Later I<br> > > > created a EVMS volume out of that. The problem I h= ad started when I<br> > > > tried to format the partition, something like:<br> > > > <br> > > > FSIM Plug-in NSSFS returned error code 1 when called to = mkfs on<br> > > > volume /dev/evms/homes<br> > > > <br> > > > Can anyone help me??<br> > > > <br> > > > Thanks ....<br> > > <br> > > What file system were you trying to put on the volume? = EVMS does not<br> > > ship support for an NSSFS file system. What happens if = you try to put<br> > > a different file system on the volume?<br> > > <br> > > Steve D.<br> </tt><br> <tt>Try running the mkfs from a command line outside of EVMS, e.g., &qu= ot;mke2fs /dev/evms/home" and see if it gives you any informative = error messages. You might also take a look at the EVMS log, /var/= log/evms-engine.log, and see if there are any helpful messages. F= irst search for "commit_changes" to get to the part where EVM= S is applying the changes. Then search for "mkfs". &nbs= p;You can also try running with the debug level set to "debug"= ; to put more detailed messaged into the log. For example, run &q= uot;evmsgui -d debug".</tt><br> <br> <tt>Steve D.</tt></body></html>= --0__=09BBFFB0DFEDF5FA8f9e8a93df938690918c09BBFFB0DFEDF5FA-- --===============5429659855546639931== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ --===============5429659855546639931== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Evms-devel mailing list [email protected] To subscribe/unsubscribe, please visit: https://lists.sourceforge.net/lists/listinfo/evms-devel --===============5429659855546639931==--