Displaying 10 results from an estimated 10 matches for "d_time".
Did you mean:
_time
2009 Sep 04
3
2.6.31-rc8: CIFS with 5 seconds hiccups
...e kernel: fs/cifs/transport.c: Sending smb: total_len 104
---- 5 second hiccup
Sep 4 16:21:48 rd-spare kernel: fs/cifs/connect.c: rfc1002 length 0xce
Sep 4 16:21:48 rd-spare kernel: fs/cifs/connect.c: rfc1002 length 0xc0
Sep 4 16:21:48 rd-spare kernel: fs/cifs/inode.c: inode 0xf5876518 old_time=26000 new_time=32751
Sep 4 16:21:48 rd-spare kernel: fs/cifs/inode.c: cifs_revalidate - inode unchanged
Sep 4 16:21:48 rd-spare kernel: fs/cifs/file.c: CIFS VFS: in cifs_writepages as Xid: 264 with uid: 0
Sep 4 16:21:48 rd-spare kernel: fs/cifs/file.c: CIFS VFS: leaving cifs_writepages (xid =...
2014 Apr 18
0
Re: Many orphaned inodes after resize2fs
...how many inodes
you had after the resize, and what file system features might have
been enabled on your file system.
If the only file system corruption errors that you saw were from about
the corrupted orphan inode list, then things are probably OK.
What this error message means is that there are d_time values which
look like they belong to inode numbers (as opposed to number of
seconds since January 1, 1970). So if you ran the system where the
clock was set incorrectly, so that the time was January 1, 1970, and
you delete a lot of files, you can run into this error --- it's
basically a sanit...
2014 Apr 18
3
Re: Many orphaned inodes after resize2fs
...r the resize, and what file system features might have
> been enabled on your file system.
>
> If the only file system corruption errors that you saw were from about
> the corrupted orphan inode list, then things are probably OK.
>
> What this error message means is that there are d_time values which
> look like they belong to inode numbers (as opposed to number of
> seconds since January 1, 1970). So if you ran the system where the
> clock was set incorrectly, so that the time was January 1, 1970, and
> you delete a lot of files, you can run into this error --- it'...
2014 Apr 18
2
Many orphaned inodes after resize2fs
Hello,
yesterday I experienced following problem with my ext3 filesystem:
- I had ext3 filesystem of the size of a few TB with journal. I correctly
unmounted it and it was marked clean.
- I then ran fsck.etx3 -f on it and it did not find any problem.
- After increasing size of its LVM volume by 1.5 TB I resized the
filesystem by resize2fs lvm_volume and it finished without problem.
- But
2017 Oct 18
0
dfs links anywhere?
...e.*
>
> msdfs root = yes, link points to path, link CANNOT be followed
> trace_msdfsrootyes_path.*
In this one I still see things mixing directory separators, e.g.:
Update attributes: //smb03.physics.wisc.edu/smb\instr_files inode
0xffff893c53c0e0a8 count 1 dentry: 0xffff893c596bbd80 d_time 0 jiffies
5742081270
What about making your symlink like this:
ln -s 'msdfs:\\smb03.physics.wisc.edu\share\path' testback
Note the use of simple quote and double _back_slash. I get unexpected
result with zsh (\ gets interpreted..) but with bash it results in this:
d55:/tmp/sh...
2008 Aug 13
1
CIFS mount problems
...] /build/buildd/linux-2.6.24/debian/build/custom-source-xen/fs/cifs/inode.c: CIFS VFS: in cifs_revalidate as Xid: 911 with uid: 0
> [31332.152635] /build/buildd/linux-2.6.24/debian/build/custom-source-xen/fs/cifs/inode.c: Revalidate: inode 0xffff88001b812cb8 count 1 dentry: 0xffff88001b817560 d_time 0 jiffies 4302758578
> [31332.152638] /build/buildd/linux-2.6.24/debian/build/custom-source-xen/fs/cifs/inode.c: Getting info on
> [31332.152641] /build/buildd/linux-2.6.24/debian/build/custom-source-xen/fs/cifs/cifssmb.c: In QPathInfo (Unix) the path
> [31332.152643] /build/buildd/linu...
2017 Sep 26
5
dfs links anywhere?
(Let's keep this on the list)
Aurélien Aptel via samba <samba at lists.samba.org> writes:
> Chad William Seys <cwseys at physics.wisc.edu> writes:
>> Somehow the destination having 'msdfsroot yes' prevents the cifs kernel
>> module from following the link.
I've taken a look at your traces and right off the bat I see things like
this:
[...]
2019 Feb 14
3
32 seconds vs 72 minutes -- expected performance difference?
Saurabh Nanda <saurabhnanda at gmail.com> writes:
> I found something interesting in /proc/fs/cifs/Stats. Notice the
> "QueryDirectories > Failed" number. This keeps increasing as along as `ls
> -lR` is running.
That's interesting indeed. The verbose logs and network trace would tell
us more.
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97
2019 Feb 15
0
32 seconds vs 72 minutes -- expected performance difference?
...ce kernel: [57077.482879]
/build/linux-Y38gIP/linux-4.15.0/fs/cifs/dir.c: name: \shared\debug.log
Feb 15 05:41:09 prod-backoffice kernel: [57077.485886]
/build/linux-Y38gIP/linux-4.15.0/fs/cifs/inode.c: Update attributes:
\shared\debug.log inode 0x00000000e2b41764 count 1 dentry:
0x00000000b5a5453d d_time 0 jiffies 4309162152
Feb 15 05:41:09 prod-backoffice kernel: [57077.492014]
/build/linux-Y38gIP/linux-4.15.0/fs/cifs/inode.c: Getting info on
\shared\debug.log
Feb 15 05:41:09 prod-backoffice kernel: [57077.495222]
/build/linux-Y38gIP/linux-4.15.0/fs/cifs/smb2pdu.c: create/open
Feb 15 05:41:09 prod...
2001 Mar 13
5
is this null block OK?
...struct dentry *dentry,
struct rec_info *rec)
{
struct journal_suffix s;
struct journal_prefix *p = (struct journal_prefix *)log;
if ( dentry ) {
s.prevrec = cpu_to_le32(rec->offset - dentry->d_time);
dentry->d_time = (unsigned long) rec->offset;
} else {
s.prevrec = -1;
}
s.recno = cpu_to_le32(rec->recno);
s.time = cpu_to_le32(CURRENT_TIME);
s.len = cpu_to_le32(p->len);
return logit(buf, &s, sizeof...