search for: no_wdelay

Is there a trick to copy files via smbfs and keep uid/gid/permissions? Usually uid/gid/permission of a transfered file depends on the uid used when mounting the remote share. But maybe there is a trick/patch whatever ... background: I'd like to use a linux-based NAS to backup loads of files *including their permissions and uid/gid*. The NAS supports NFS (which can do what I want) but the

...have tried many different nfs server options and other nfs client options. I also set up a test nfs server with centos4 and 5 where I am the only user, and while copying big chunks of date, nfs freezes (hangs) too. Here is my /etc/exports: /home *domain.com(rw,root_squash,sync,no_subtree_check,no_wdelay) Here is how client workstations mount the export in the fstab fshome:/home /home/ nfs rsize=8192,wsize=8192,intr 0 0 Am I mis-configuring the nfs server of clients? Is there anything I am not doing right? If anybody has any suggestions, I would appreciate it very much. Thanks, Jean Fig...

...ny problems. Depending on the nature of the journal (metadata journaling and/or data journaling), we may have little or no data loss. Bill Rigolsky, also pointed out that I may have some performance benefits from data=journal option, since I am exporting the EXT3 filesystem with the "rw,sync,no_wdelay" options, thus forcing NFS to do synchronous commits. His reasoning is based on a theory that with "data=ordered" and "sync" options for EXT3 and NFS, the system will have to work harder to write out data blocks and may need to "seek all over the disk to do so."...

...nts yields: /dev/sdb1 /nas ext3 rw 0 0) the unit at any give time. The other box listens, via heartbeat (linux-ha), waiting to mount the RAID unit, should it''s sibling crash (actually, heartbeat no longer heard via serial and ethernet). The /nas directory is NFS exported with the rw,sync,no_wdelay options to several Linux and Tru64 boxes. Questions: ---------- What will I encounter should the primary (i.e. box currently mounting /dev/sdb1) crash, and the backup take over? From my simulations, I see the backup mount /dev/sdb1 but I get the following in it''s /var/log/messages: nas2...

Hello, as far as I understood ext3 will more or less hog a machine when writing away the journal. A customer is having a slowdown every 5 minues for about 30 seconds, the machine becomes more or less unusable. This is an NFS server serving 300 Gigs spread over 2 NFS shares. I'm wondering what would be the best course of action: a) make the journal bigger? b) make the journal smaller?