Re: inode issue with cifs

To: Little Bill <littlebill2121@gmail.com>
Cc: debian-user@lists.debian.org
Subject: Re: inode issue with cifs
From: Dan Ritter <dsr@randomstring.org>
Date: Sat, 22 Jan 2022 11:28:23 -0500
Message-id: <[🔎] 20220122162823.o2ttvn5e4dgajybe@randomstring.org>
In-reply-to: <CAA+6DDWq-Mr5SxLtD1jkDFncOe1kYGxj7o5kc1e4wUPbbFqyRw@mail.gmail.com>
References: <[🔎] CAA+6DDXkTcN43qQnzTFgEmmZFGbATCWUVz6AWmhW20sYDMK-zQ@mail.gmail.com> <[🔎] 20220122155023.ivlmeeh2gj6bwsg5@randomstring.org> <CAA+6DDWq-Mr5SxLtD1jkDFncOe1kYGxj7o5kc1e4wUPbbFqyRw@mail.gmail.com>

Little Bill wrote: 
> Provided the mount?  This inode issue doesn't occur on Debian 8 and nfs. To
> the same nas and content

Then why don't you try it with NFS and see if two networked
filesystems give the same results or different results?

-dsr-

Reply to:

Follow-Ups:
- Re: inode issue with cifs
  - From: Little Bill <littlebill2121@gmail.com>

References:
- inode issue with cifs
  - From: Little Bill <littlebill2121@gmail.com>
- Re: inode issue with cifs
  - From: Dan Ritter <dsr@randomstring.org>

Prev by Date: Re: firejail: changing Ethernet network adapter name is breaking Firefox profile
Next by Date: Re: firejail: changing Ethernet network adapter name is breaking Firefox profile
Previous by thread: Re: inode issue with cifs
Next by thread: Re: inode issue with cifs
Index(es):
- Date
- Thread