| To: | "Christian, Chip" <chip.christian@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs + knfsd w/ sync exports |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | Fri, 27 Apr 2001 11:37:58 -0500 |
| Cc: | "Linux XFS (E-mail)" <linux-xfs@xxxxxxxxxxx>, "NFS list (E-mail)" <nfs@xxxxxxxxxxxxxxxxxxxxx> |
| In-reply-to: | Message from "Christian, Chip" <chip.christian@storageapps.com> of "Fri, 27 Apr 2001 11:44:56 EDT." <23D04BDBA646D411BDDD00D0B774B539028C882D@SA-BWMAIL1> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
> The answer could very well be "don't use sync exports with a journaling files > ystem", but I thought I'd throw this out there so it's at least a documented > restriction... > > I'm running 2.4.2-SGI_XFS_0.10.4d1 with knfsd, supporting NFS v3. Mounted a > XFS filesystem through RedHat's new multipath code, exported the filesystem ( > rw,no_subtree_check,sync). > A fix will show up in the development cvs tree shortly, and will be in the next spin of the rpm images. This was a case of the fsync code not being brought upto date with kernel interface changes over time - the only place it mattered from is sync NFS. Time to go beat up the tester who was running NFS tests - looks like mount options were not on his list. Steve |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Blantant disregard for content topic: I need a job ..., Bryan J. Smith |
|---|---|
| Next by Date: | TAKE - fix nfs sync exports for xfs, Steve Lord |
| Previous by Thread: | Re: xfs + knfsd w/ sync exports, Steve Lord |
| Next by Thread: | RE: xfs + knfsd w/ sync exports, Christian, Chip |
| Indexes: | [Date] [Thread] [Top] [All Lists] |