On Aug 19, 2008 14:59 +0200, Philippe Weill wrote:
> I put the journal on LVM over multipath for my OSTs
>
> formating the OST was made with
>
> mkfs.lustre -v --reformat --fsname=datafs --ost --mgsnode=10.0.0.1
> --mgsnode=10.0.0.2 --failover=10.0.0.3 --mkfsoptions="-E stride=64 -E
> stri
Thanks Andreas.
Is this documented anywhere? We are facing inode shortage problems on
our filesystem and I would like to show this to my professors. The
reason why this is occurring is..
I checked the operations manual and Lustre "inter galactic" file
system but no luck of this issue.
TIA
On
Hello,
we're seing an LBUG on clients running with Lustre 1.6.5.1 (the servers are
still under 1.6.4.3). I tried finding this in bugzilla with no success. There
seems to be some data inconsistency, can somebody please tell me whether this
is rather on the server side (the data on disk is inconsist
On Wed, 2008-08-20 at 16:00 +0200, Erich Focht wrote:
> Hello,
>
> we're seing an LBUG on clients running with Lustre 1.6.5.1 (the servers are
> still under 1.6.4.3). I tried finding this in bugzilla with no success.
Bug 16427.
b.
signature.asc
Description: This is a digitally signed message
On Tue, 2008-08-19 at 19:42 -0400, Christopher Walker wrote:
> Hello,
Hi,
> (In the logs above 10.242.40.14 = herologin1). Should I try the
>
> echo 0 > /proc/fs/lustre/llite/*/statahead_max
>
> solution that fixed the statahead problem?
It's surely worth a try, in an attempt to try to isolat
On Mittwoch 20 August 2008, Brian J. Murrell wrote:
> On Wed, 2008-08-20 at 16:00 +0200, Erich Focht wrote:
> > Hello,
> >
> > we're seing an LBUG on clients running with Lustre 1.6.5.1 (the servers are
> > still under 1.6.4.3). I tried finding this in bugzilla with no success.
>
> Bug 16427.
Th
On Wed, 2008-08-20 at 16:47 +0200, Erich Focht wrote:
>
> Thanks but... I don't seem to be authorized to see that bug (?).
Oh, yes. :-( I tend to forget to look at the privacy settings on bugs.
> Is that bug fixed in 1.6.5.1?
No. Reported on 1.6.5 in fact.
> Any advice resulting from its co
Hi there
I got the following background information from Juergen Kreuels at SGI
"It turned out that a bad disk ( which did NOT report itself as being
bad ) killed the lustre leading to data corruption due to inode areas on
that disk.
It was finally decided to remake the whole FS and only during
Oh damn, I'm always afraid of silent data corruptions due to bad harddisks. We
also already had this issue, fortunately we found this disk before taking the
system into production.
Will lustre-2.0 use the ZFS checksum feature?
Thanks,
Bernd
On Wednesday 20 August 2008 19:08:34 Peter Jones wro
On Aug 20, 2008 06:45 -0400, Mag Gam wrote:
> Is this documented anywhere? We are facing inode shortage problems on
> our filesystem and I would like to show this to my professors. The
> reason why this is occurring is..
Well, according to the "lfs df -i" output below there are lots of inodes
fr
On Thu, 2008-08-14 at 08:05 -0400, Mag Gam wrote:
> What is the disadvantage of creating a MDS partition with smaller
> inodes per block? Now, its 4k per inode what happens if we go to the
> least blocks which is 1024k?
You risk running out of room in the inode for EAs, requiring that
another bloc
> > them up. You are now ready to use Lustre Debian style. If deploying this on
> > a cluster, just install your ready made .debs for the kernel and modules.
> > None of this was explained in the README in /usr/share/doc/Lustre so we had
> > to figure it out ourselves. Hopefully the Debian folks ha
On Aug 20, 2008 17:40 -0500, Troy Benjegerdes wrote:
> > > them up. You are now ready to use Lustre Debian style. If deploying this
> > > on
> > > a cluster, just install your ready made .debs for the kernel and modules.
> > > None of this was explained in the README in /usr/share/doc/Lustre so w
That makes more sense. Is there a more updated resource than:
http://wiki.lustre.org/index.php?title=Lustre_Quick_Start
On Wed, Aug 20, 2008 at 05:17:57PM -0600, Andreas Dilger wrote:
> On Aug 20, 2008 17:40 -0500, Troy Benjegerdes wrote:
> > > > them up. You are now ready to use Lustre Debian
On Aug 20, 2008 18:24 -0500, Troy Benjegerdes wrote:
> That makes more sense. Is there a more updated resource than:
>
> http://wiki.lustre.org/index.php?title=Lustre_Quick_Start
Ugh, that is only for 1.4, and needs a refresh. Try the Lustre manual:
http://manual.lustre.org/
Cheers, Andreas
--
Brian:
What is an EA?
Yes. We create 20k files per day. Multiple that by 360days per year
(for our research), thats about 7200 files per year
We have 11 years of data. 79200 files
OUr file size range from 5M to 70M (average)
I know its crazy but a professor or studeny will need any of
Hi, all,
I got a problem when I testing lustre-1.6.5.1 on CentOS-5.2.
I have four machines(PCs), they are MGS co-located with MDT, OSS-1, OSS-2 and
CLT.
OSS-1 have two disks which are formatted as ost01(40GB) and ost02(15GB).
OSS-2 have two disks which are formatted as ost03(23GB) and ost04(5GB)
If I understand right when you use 'setstripe -c -1' lustre will try
to evenly spread the data of a file over all OST's.
Because one of yours gets full, the file can nolonger be added to.
Lustre does not fall back to using fewer stripes as most users say
'use more stripes' for a reason.
On Aug 18, 6:43 am, Andreas Dilger <[EMAIL PROTECTED]> wrote:
> On Aug 09, 2008 05:06 -0700, daledude wrote:
>
> > Is there is a tool that shows what files are being accessed? Sort of
> > like inotify, but not inotify? I'd like to compile file access
> > statistics to try and balance the most ac
On Aug 20, 2008 13:58 -0700, daledude wrote:
> On Aug 18, 6:43 am, Andreas Dilger <[EMAIL PROTECTED]> wrote:
> > On Aug 09, 2008 05:06 -0700, daledude wrote:
> >
> > > Is there is a tool that shows what files are being accessed? Sort of
> > > like inotify, but not inotify? I'd like to compile fil
Hello,
we use LUSTRE with AUTOFS to circumvent (hopefully) the evicted client
statahead problem and disconnect lustre client when not in use.
We get the following messages just before the client is unmounted. It is
reproducable and happens every unmount.
The functionality of further client mou
Hi All
I have Lustre setup in ESX Sever 3.5.0 as a Host with 3 CentOS with the
following kernel
# uname -a
Linux oss.sun.com 2.6.9-67.0.7.EL_lustre.1.6.5.1smp #1 SMP Wed Jun 18
19:11:19 EDT 2008 i686 i686 i386 GNU/Linux
Thanks and Regards
Confing as under
1 MDS and MGS on same
22 matches
Mail list logo
