On 2022/01/31 13:36, Adam Dinwoodie wrote:
Could it be that the first 'mv' triggered an anti-virus read of the file since
perhaps it detects it as a new/changed file?
But if so, would 'mv' (under Task Manager) be showing the 100+ MB/s disk
activity?
That definitely seems plausible;
Greetings, cyg...@kosowsky.org!
> I literally am typing something like:
> mv foo bar
> In Linux, that just edits the file system table & inode...
> UPDATE...
> I just tried a second 'mv' and it was near instantaneous.
> (and similarly with subsequent renaming of the same file)
> So perhaps
On Mon, Jan 31, 2022 at 10:17:59AM -0500, cyg...@kosowsky.org wrote:
> Eliot Moss wrote at about 09:59:17 -0500 on Monday, January 31, 2022:
> > On 1/31/2022 9:52 AM, cyg...@kosowsky.org wrote:
> > > I tried renaming some very large files (20-40 GB) using:
> > > mv
> > > without
>
> In my case the directory (where I renamed the file) is on my C-drive.
>
If the file is currently open for access, the move can turn out to be a copy,
actually.
Check open files to make sure whatever you are moving is not being opened /
accessed from any other program.
Anton Lavrentiev
René Berber wrote at about 09:13:59 -0600 on Monday, January 31, 2022:
> On 1/31/2022 8:59 AM, Eliot Moss wrote:
>
> > On 1/31/2022 9:52 AM, cyg...@kosowsky.org wrote:
>
> >> I tried renaming some very large files (20-40 GB) using: mv
> >> without changing the directory of course.
> >>
Eliot Moss wrote at about 09:59:17 -0500 on Monday, January 31, 2022:
> On 1/31/2022 9:52 AM, cyg...@kosowsky.org wrote:
> > I tried renaming some very large files (20-40 GB) using:
> > mv
> > without changing the directory of course.
> >
> > The process took about 10-20 minutes
On 1/31/2022 8:59 AM, Eliot Moss wrote:
On 1/31/2022 9:52 AM, cyg...@kosowsky.org wrote:
I tried renaming some very large files (20-40 GB) using: mv
without changing the directory of course.
The process took about 10-20 minutes with Task Manager showing
disk activity of 100+ MB/s.
Is
On 1/31/2022 9:52 AM, cyg...@kosowsky.org wrote:
> I tried renaming some very large files (20-40 GB) using:
> mv
> without changing the directory of course.
>
> The process took about 10-20 minutes with Task Manager showing disk
> activity of 100+ MB/s.
>
> Is there something about such
I tried renaming some very large files (20-40 GB) using:
mv
without changing the directory of course.
The process took about 10-20 minutes with Task Manager showing disk
activity of 100+ MB/s.
Is there something about such large 'renaming' that actually results
in the file being really
9 matches
Mail list logo
