Displaying 6 results from an estimated 6 matches for "smb_proc_setattr_ext".
2002 Dec 16
1
Create time changing by itself?
Are there some known problems related to ctime changing by itself? I
didn't find anything with google at least. tar seems to be complaining
about it all the time:
[cras@hurina] ~% tar cf test.tar /mnt/cygwin/home
tar: Removing leading `/' from member names
tar: /mnt/cygwin/home/Timo Sirainen/xxx/xxxxx.xxx: file changed as we read it
This happens with my Debian/unstable (samba
2005 Jan 04
0
[2.6 patch] smbfs: make some functions static
...block *sb, void *raw_data, int silent)
{
struct smb_sb_info *server;
struct smb_mount_data_kernel *mnt;
--- linux-2.6.10-mm1-full/fs/smbfs/proc.c.old 2005-01-04 00:58:37.000000000 +0100
+++ linux-2.6.10-mm1-full/fs/smbfs/proc.c 2005-01-04 00:59:12.000000000 +0100
@@ -74,7 +74,7 @@
static int
smb_proc_setattr_ext(struct smb_sb_info *server,
struct inode *inode, struct smb_fattr *fattr);
-int
+static int
smb_proc_query_cifsunix(struct smb_sb_info *server);
static void
install_ops(struct smb_ops *dst, struct smb_ops *src);
@@ -2075,7 +2075,7 @@
return result;
}
-void smb_decode_unix_basic(stru...
2002 Oct 28
3
SMBFS files receiving incorrect timestamps
Hello all.
Our system consists of two linux machines, each running Red Hat 7.1
(kernel 2.4.9-34), using SMB to mount multiple shares hosted by a
Windows 2000 Advance Server. smbclient from Samba 2.2.5 is used to do
the actual mounting.
Over the weekend, a number of files on these SMBFS shares were created
with incorrect timestamps (modification times). In some cases, the
timestamps were off by
2002 Dec 21
0
Re: samba digest, Vol 1 #2006 - 24 msgs (Out of the office - Returning Monday, Jan. 6th)
...his, and still tar thinks the file was modified. Now I'm seeing
the
ctime drift like Timo noticed when I stat. The first stat showed one
ctime
and then the next and subsequent stat's showed an mtime 2 seconds into
the
future from the first. They were all even second mtimes.
> - remove smb_proc_setattr_ext()
I skipped this and went to the next step, then came back to this step.
Everything seems to be the same. I get the file changed as we read it
msg
while in the create stage, and Mod time differs while in the verify
stage.
> - replace ino->i_mtime in the smb_proc_close() call with a 0
I did...
2000 Jun 28
1
[Patch] Shorter patch for smbfs 2.2.16
...+ if ((server->opt.protocol >= SMB_PROTOCOL_LANMAN2) &&
+ !(ino->u.smbfs_i.access == SMB_O_RDONLY))
+ {
struct smb_fattr fattr;
smb_get_inode_attr(ino, &fattr);
smb_proc_setattr_ext(server, ino, &fattr);
@@ -903,8 +931,11 @@
ino->i_mtime);
ino->u.smbfs_i.cache_valid &= ~SMB_F_LOCALWRITE;
/*
- * Force a revalidation after closing
+ * Force a revalidation a...
2003 Dec 01
0
No subject
...anges to whatever kernel you use.
The changes are to smb_proc_close_inode.
/Urban
--- linux-2.4.7-pre6-orig/fs/smbfs/proc.c Wed Jul 4 17:09:28 2001
+++ linux/fs/smbfs/proc.c Fri Jul 13 13:15:37 2001
@@ -1111,6 +1111,12 @@
struct smb_fattr fattr;
smb_get_inode_attr(ino, &fattr);
smb_proc_setattr_ext(server, ino, &fattr);
+
+ /* set the archive bit if we modified the file */
+ if (ino->flags & SMB_F_LOCALWRITE) {
+ fattr.attr |= aARCH;
+ smb_proc_setattr(server, ino, &fattr);
+ }
}
result = smb_proc_close(server, ino->u.smbfs_i.fileid,
Return-Path: <urb...