I did the xfs_repair this morning (first -n, ...). It worked fine, didn't
spit out anything in particular (but i kept the output in case someone's
interested). I can access those dirs again, all data seems to be there.
The patch you gave me below was already installed in xfs_inode.c
(1.3.0pre2), so that shouldn't have been the issue.
I'm getting XFS 1.2 in RH 2.4.2(0|1) kernel ready for next wednesday's
downtime. Should the cmd-rpms for 1.3.0pre2 work with XFS1.2 kernel, or
should i be cautious and switch each time i change kernel? I currently
have:
xfsprogs-2.4.12-0
xfsdump-2.2.12-0
xfsprogs-devel-2.4.12-0
thanks for all the help and suggestions and bringing this excellent fs to
linux!
-seb.
On Tue, 1 Jul 2003, Sebastien Boving wrote:
>
> On Wed, 2 Jul 2003, Nathan Scott wrote:
>
> > Looks alot like a sync/iget interaction bug we were seeing recently -
> > Steve fixed this a couple of weeks ago, the change was:
> >
>
>
> i was doing a lot of writes (40mb/s, probably as much writes as this
> stripe of 2 serial ATA's raid5's can take), and i have big write
> caches, i think (logbufs=8,logbsize=32768 as recommended in faq).
>
> i'll try the patch out, thanks.
>
>
> > --- /usr/tmp/TmpDir.2068614-0/linux/fs/xfs/xfs_inode.c_1.376 Wed Jul
> > 2 08:51:27 2003
> > +++ /usr/tmp/TmpDir.2068614-0/linux/fs/xfs/xfs_inode.c_1.377 Wed Jul
> > 2 08:51:27 2003
> > @@ -2629,7 +2629,8 @@
> > if (vp) {
> > struct inode *inode = LINVFS_GET_IP(vp);
> >
> > - mark_inode_dirty_sync(inode);
> > + if (!(inode->i_state & I_NEW))
> > + mark_inode_dirty_sync(inode);
> > }
> >
> > wake_up(&ip->i_ipin_wait);
> >
> >
> > cheers.
> >
> >
>
>
|