Filenames on 'server' jobs to shared filesystems

Filenames on 'server' jobs to shared filesystems

[Matthew Richardson]

[-- Attachment #1: Type: text/plain, Size: 892 bytes --]

I'm currently using fio to simulate user reads and writes to a NAS
service, and am testing the performance of different shared filesystems
(NFS, Samba, Glusterfs etc).

In order to properly load the box I'm using a pool of clients to connect
to the fs (fio --server) and then launching the same job on multiple
clients. (fio --client=a --client=b job.fio)

The resulting jobs on the different servers all seem to use the same
file - the filename seems to be <name>.<thread>.<fileno> - in this case
'job.1.0':

[global]
directory=/mnt/gluster
rw=randrw
size=10M
ioengine=libaio

[job]


Is there any way to have the server include some personal identifier
(such as hostname) in the filename so that there isn't this conflict?

Thanks,

Matthew

-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: Filenames on 'server' jobs to shared filesystems

[Jens Axboe]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2012-07-17 17:19, Matthew Richardson wrote:
> I'm currently using fio to simulate user reads and writes to a NAS
> service, and am testing the performance of different shared filesystems
> (NFS, Samba, Glusterfs etc).
> 
> In order to properly load the box I'm using a pool of clients to connect
> to the fs (fio --server) and then launching the same job on multiple
> clients. (fio --client=a --client=b job.fio)
> 
> The resulting jobs on the different servers all seem to use the same
> file - the filename seems to be <name>.<thread>.<fileno> - in this case
> 'job.1.0':
> 
> [global]
> directory=/mnt/gluster
> rw=randrw
> size=10M
> ioengine=libaio
> 
> [job]
> 
> 
> Is there any way to have the server include some personal identifier
> (such as hostname) in the filename so that there isn't this conflict?

That's not a bad idea, to have the backend prefix with it's hostname or
similar. Let me know if you want to test (or create!) such a patch, I'd
be happy to help.

Sorry about the late response - that goes to all the emails on this
list. I've been away on business and then vacation, so it's been a while
and I'm trying to catch up.

- -- 
Jens Axboe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJQGC7rAAoJEPfTWPspceCm5cYQAMqHqMYzEMNT6xEUBUHvuRON
ZlOhAqHP191vWLDTGvbSmkDZEerd5uQULbVhWDtvdgrnfivtjv91NhQnN9D4RY7P
YNQfLXyPUHkYnc4271XqFxNnwCwQ0nNklGL3nUsGHdlHxK2nrDAsFxkMoPUkNZP+
pAS2Gpg3Enz9O0sBmeIFQpTv478RKwD8tgHEQKn/ZusRKo5XlJNBfjOJhP/oEfny
l3C7s1rhfHCsnIVL1M/AWdA+1tp8+h+byxOz49IIGa/fif0P+eCgihuU/UohDsFE
sNe2jBoXfXvW3zHYA8nUzL9vjZjLQFKgTBWldM1nuxz2SMA66O40K0BZ6x1hIOaJ
fJafWhflPNBSJBxuvwLBzGv4hsfwp0ABBCZG0uz2brLUFog3Yr+qqRJAy6yIWjmK
Ha3jaPV3sVD1cjV+xaNLdLv2QsEIAo3gghZyIFskuW+NuNkH9icgwo+i5Owl+4ER
v6c4ydcPtdJFguotOG6D4kgfl358pLfwSWTzKK3P7uve3xuAjxKdMVjgLE92/MCn
pxvOmws0hn5m3+thmodbi8ipKsHvALl+IYidWKdWAEqVz0LUGRjrZWxHxA5dX/+l
vHJjmnUvk2rI+Tzakuli9PZap7r4uieC1IfHm4gdOJKrGHztBH4yVjz9V+zsEjF/
Uwm1vfkoiwwbhkVAMxYf
=3u9j
-----END PGP SIGNATURE-----