Drew: I had sent Erik a wad of changes that added a "raw:" syntax to enable raw 
devices in the path string. Do you know if that was integrated?

Thanks,

Richard.


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:perf-discuss-
> [EMAIL PROTECTED] On Behalf Of Andrew Wilson
> Sent: Monday, November 24, 2008 7:25 AM
> To: Demetri S. Mouratis
> Cc: perf-discuss@opensolaris.org
> Subject: Re: [perf-discuss] filebench source hints at raw device
> support
> 
> On 11/21/08 15:09, Demetri S. Mouratis wrote:
> > Dear filebench gang,
> >
> > fileset.c shows some evidence of a way to use filebench against
> individual raw device files instead of the 00000001/00000001 directory
> structure implied by fileset names.  I've been staring at it an hour or
> more, and I can't figure out how to make it work.
> >
> > I've actually been trying to hack together a raw test by pre-creating
> a directory tree where the last 00000001 file is actually a symlink to
> /dev/vx/rdsk/demetridg/volume00.
> >
> > Unfortunately, I can only kinda make it work using multiple 'define
> file' statements and hand-create each of the threads where each refers
> to one of the files.  Plus, something makes me pre-allocate it, which
> is really, really slow for lots of 32GB devices.
> >
> > Any hints?
> >
> > ...Demetri
> >
> Demetri,
>    Use the "define file" option and use the path to raw devices and the
> raw device name with it. For instance
> 
> define file name=c2t0d0s2, path=/dev/dsk
> 
> FileBench will detect that this is a raw disk partition and open it as
> such. As long as you are super user you will be able to read and write
> to it, so be CAREFUL what you do!!!
> 
> A fileset of multiple raw devices would also be nice, but we don't have
> that yet, so you will have to access each raw device as a separate file
> for now.
> 
> Drew
> 
> 
> 
> _______________________________________________
> perf-discuss mailing list
> perf-discuss@opensolaris.org
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org

Reply via email to