+1 on
options zfs zfs_prefetch_disable=1
Might not be as critical now, but that was a must-have on Lustre 2.5.x
Tim
From: lustre-discuss On Behalf Of
Riccardo Veraldi
Sent: Wednesday, March 13, 2019 3:00 PM
To: Kurt Strosahl ; lustre-discuss@lists.lustre.org
Subject: Re: [lustre-discuss] ZFS
these are the zfs settings I use on my MDSes
zfs set mountpoint=none mdt0
zfs set sync=disabled mdt0
zfs set atime=off amdt0
zfs set redundant_metadata=most mdt0
zfs set xattr=sa mdt0
if youor MDT partition is on a 4KB sector disk then you can use
ashift=12 when you create the filesystem
Good Afternoon,
I'm reviewing the zfs parameters for a new metadata system and I was
looking to see if anyone had examples (good or bad) of zfs parameters? I'm
assuming that the MDT won't benefit from a recordsize of 1MB, and I've already
set the ashift to 12. I'm using an MDT/MGS made
Excellent. That should work great.
-Paul Edmon-
On 3/13/19 10:25 AM, Chad DeWitt wrote:
Hi Paul,
lfs findmay do what you want:
lfs find /lustre_mount_point/ --ost /IDs_of_OSTs/
/
/
/IDs_of_OSTs/is comma delimited
Should even grab files that are striped and have a portion
Hi Paul,
lfs find may do what you want:
lfs find *lustre_mount_point* --ost *IDs_of_OSTs*
*IDs_of_OSTs* is comma delimited
Should even grab files that are striped and have a portion of their data on
the specified OSTS.
-cd
Chad
I have a OSS that is offline. Is there a way to poll the MDT and grab a
list of files that are on the affected OST's? Or is the only method
just scaning the whole filesystem with normal find combined with lfs
getstripe commands?
-Paul Edmon-
___
Hi everyone,
I'm running a Lustre 2.10.6 file system with two MDS. One of them has
just crashed, I have received these messages:
Message from syslogd@miscmds4 at Mar 13 09:01:24 ...
kernel:[5584275.388034] LustreError:
321079:0:(lod_object.c:1584:lod_parse_dir_striping()) ASSERTION(
