On Wednesday 19 December 2001 12:11 pm, Ed Tharp wrote: > I guess if the partitions were all "clean" setup and all, I was wrong > guessing the difference, and the cause of the 150 or so lines of "clm-6005: > writing inode 52808 on readonly FS" in dmesg is still a mistery > > If you don't mind I will post this question to the list, if Civileme > is answering questions on the > list, you can not get a more definitive answer than one from him. > The ReiserFS - NFS problems are pretty well documented. but are not a > problem except for NFS mounts, any NFS mounts can be on a non-ReiserFS with > no problems, as I understand it, (and hoping to be corrected) (it is just > the way NFS writes to the file I believe) > > see http://mandrakeforum.com/article.php?sid=1124&lang=en for some of the > info. I know this is talking about "cooker" or crashtesting, but the info > is about the same IMHO. > > " The test program completes uneventfully on ext3, ext3 over NFS, reiserfs > (but not reiser over NFS--the NFS freezes even though there is no reiser > corruption), ext2 (if you have a big enough partition to hold 100,000 > inodes), and ext2 over NFS." > > On Wednesday 19 December 2001 07:25, you wrote: > > The reiserfs disks were all created with 8.1. I did a totally fresh > > install with it on the server - scrubbing the disks and creating new > > partitions during the install and built the client machine from scratch > > just recently, so it's never had any version but 8.1 installed. > > In any case, the NFS issue is of concern. Is this documented anywhere > yet, > > > or just filtering through the grapevine? What would you suggest in its > > place - ext3? > > > > > > Again on the NFS issue - I presume that its effect is limited to the > > reiserfs disks which have exported directories? i.e. if I limited the > > exports to say hdb with some different NFS compatible fs, and left hda > > with reiser and no exports, would you see a problem there? > > > > > > resolv.conf reads: > > > > search homelan.org > > nameserver 192.189.54.26 > > nameserver 192.189.54.37 > > nameserver 192.168.0.1 > > Homelan is not your isp? put the ISP name there instead > if homelan.org is your ISP, the nameserver numbers are wrong. > Whois Search Results; homelan.org > > Server Name: NS1.IQUEST.NET > IP Address: 198.70.36.70 > Registrar: NETWORK SOLUTIONS, INC. > Whois Server: whois.networksolutions.com > Referral URL: http://www.networksolutions.com > > it occurs to me that one solution MIGHT BE (big might, and sure is a > "kludge"), as long as the ip for the nameserver is correct, to make the > file not write-able by anyone other than a user by chown and chmod? > > > on the client and the server. This works OK, but after a reboot it loses > > the 192.189 addresses. I don't know what "search homelan.org" does, or > > why it gets written there. > > > > thanks again and best regards > > Brian > > > > On Wednesday 19 December 2001 11:02 pm, you wrote: > > > I do believe the problem with the error about writing inode on read > > > only file system has to do with the version of reiser you are using > > > (was it formated from a 7.2 or earlier version of mandrake ? made for a > > > 2.2.x kernel and you are now using a 2.4.x kernel?) I would backup and > > > install the newer version, but since you need NFS mounts, I would NOT > > > use reiserFS, as it seems to have some "issues" with NFS as well as > > > postfix. as far as getting resolv.conf to stay the same, I remember > > > having that problem, but damn if I can remember the cure, right now, > > > why don't you send me a copy of the resolv.conf ?
It could be kernel dependent. Reiser claims they have solved this problem. XFS works great over NFS and tests out about as fast as Reiser on our distro, and also will work much better if you have Samba servers involved anywhere in your system. Civileme
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
