Hi,
for the notice, it seems the soft lockup bug is fixed in 2.6.12-rc2-mm3
which has been running for 8 hours now without a glitch.
Cheers,
Mik
Vladimir Saveliev a écrit :
> Hello
>
> On Thu, 2005-04-07 at 12:36, Mickael Marchand wrote:
>
>>Hi,
>>
>>I am giving a shot at reiser4 to make rsync
Kathy KN (HK) wrote:
> For your first problem,
>
> see fs/reiser4/plugin/dir/hashed_dir.c, line 540,
> comment "from_dir->i_mtime = CURRENT_TIME;" away,
> and recompile your kernel.
>
> mtime shouldn't update when you try to "mv", and thus
> will not break your backup scripts.
ho, thanks,
looks
For your first problem,
see fs/reiser4/plugin/dir/hashed_dir.c, line 540,
comment "from_dir->i_mtime = CURRENT_TIME;" away,
and recompile your kernel.
mtime shouldn't update when you try to "mv", and thus
will not break your backup scripts.
Kathy
On Apr 8, 2005 4:51 PM, Mickael Marchand
<[EMAI
hmm just got 3 more soft lookups in a few hours (2/3 hours I think) ;)
my script (attached in case you want to try it) for backups basically do:
rm -rf hourly.11
mv hourly.10 hourly.11
...
mv hourly.1 hourly.2
mv hourly.0 hourly.1
cp -al hourly.1 hourly.0
rsync [various options] /home/ hourly.0/
Hi,
Vladimir Saveliev wrote:
> Hello
>
> On Thu, 2005-04-07 at 12:36, Mickael Marchand wrote:
>
>>Hi,
>>
>>I am giving a shot at reiser4 to make rsync snapshots backups (using
>>hard links and incremental rsync).
>>this works definitely great apart from 2 minor bugs :)
>>
>>1 : it seems that mv
Hello
On Thu, 2005-04-07 at 12:36, Mickael Marchand wrote:
> Hi,
>
> I am giving a shot at reiser4 to make rsync snapshots backups (using
> hard links and incremental rsync).
> this works definitely great apart from 2 minor bugs :)
>
> 1 : it seems that mv directory/ directory2/ changes the mtim
Hi,
I am giving a shot at reiser4 to make rsync snapshots backups (using
hard links and incremental rsync).
this works definitely great apart from 2 minor bugs :)
1 : it seems that mv directory/ directory2/ changes the mtime of the
directory. This is not the case with reiser3. Is this intentional
