Prev: insserv seems broken
Next: Interesting CLI finds
From: Pete Puma on 9 Mar 2010 13:39
I changed the name of a few folders and found that the directory name was
not being changed in the simple usually-understood fashion, but that the
entire contents of the name changed folder were being MOVED to a folder with
the new name.
Did it with a folder containing gigs of video items and it took a good 5
minutes.

Is this happening to anyone else using ext4? Using open Suse for over 7
years--never saw this action before.

using 11.2, KDE 4.3.5, & ext4

Cheers
From: J G Miller on 9 Mar 2010 15:57
On Tue, 09 Mar 2010 13:39:30 -0500, Pete Puma wrote:

> I changed the name of a few folders

How did you change the name? With mv?
From: jamm on 9 Mar 2010 22:08
Pete Puma wrote:

> I changed the name of a few folders and found that the directory name was
> not being changed in the simple usually-understood fashion, but that the
> entire contents of the name changed folder were being MOVED to a folder
> with the new name.
> Did it with a folder containing gigs of video items and it took a good 5
> minutes.
>
> Is this happening to anyone else using ext4? Using open Suse for over 7
> years--never saw this action before.
>
> using 11.2, KDE 4.3.5, & ext4
>
> Cheers

I assuming you are using dolphin? Haven't seen this behavior myself. I just
tried renaming a big folder to be sure and no strangeness occured.

From: JT on 10 Mar 2010 03:57
On 09/03/10 19:39, Pete Puma wrote:
> I changed the name of a few folders and found that the directory name was
> not being changed in the simple usually-understood fashion, but that the
> entire contents of the name changed folder were being MOVED to a folder with
> the new name.
> Did it with a folder containing gigs of video items and it took a good 5
> minutes.
>
> Is this happening to anyone else using ext4? Using open Suse for over 7
> years--never saw this action before.
>
> using 11.2, KDE 4.3.5, & ext4
>
> Cheers
>
Most likely, but please confirm, you were using 'mv' to rename (under
the hood probably). Normally this does the expected rename. But if you
were to use mv to change the name so that the target is on another
mountpoint, linux would really have to move the files there. In that
case: works as designed/expected.

--
Kind regards, JT

From: Pete Puma on 11 Mar 2010 20:05
JT wrote:

> On 09/03/10 19:39, Pete Puma wrote:
>> I changed the name of a few folders and found that the directory name was
>> not being changed in the simple usually-understood fashion, but that the
>> entire contents of the name changed folder were being MOVED to a folder
>> with the new name.
>> Did it with a folder containing gigs of video items and it took a good 5
>> minutes.
>>
>> Is this happening to anyone else using ext4? Using open Suse for over 7
>> years--never saw this action before.
>>
>> using 11.2, KDE 4.3.5, & ext4
>>
>> Cheers
>>
> Most likely, but please confirm, you were using 'mv' to rename (under
> the hood probably). Normally this does the expected rename. But if you
> were to use mv to change the name so that the target is on another
> mountpoint, linux would really have to move the files there. In that
> case: works as designed/expected.
>

Renaming right on the desktop in KDE.

Since posting, I forced a fsck because any directory quirks I usually chalk
up to funky disk errors (ahh, my NTFS Windows chkdsk experience kicking in).
I renamed the same giant folder (40 gigs or so) and it merely did so, with
no HD activity.

Before the disk check, I got the pop up that shows a graphic of the copy
routine as it slowly slugged along. Not so anymore.
If that's using mv under the hood, then it is a copy and delete, but should
it go through all of that overhead? Maybe the file system saw something it
didn't like?


 | 
Pages: 1
Prev: insserv seems broken
Next: Interesting CLI finds