On 07/30/2001 05:40 PM, Manuel Krause wrote:
> On 07/30/2001 02:01 PM, Vladimir V.Saveliev wrote:
>
>> Hi
>>
>> Manuel Krause wrote:
>>
>>> If I understood you correctly: The first time after "this poweroff" the
>>> partition has to be mounted rw in order to complete the unlinks?
>>> The uncompleted unlinks I have on disk will stay until next
>>> --rebuild-tree?
>>>
>>
>> Ok, would you like to try the attached patch?
>> The
>>
>ftp.namesys.com/pub/reiserfs-for-2.4/2.4.7.pending/2.4.7-unlink-truncate-rename-rmdir.dif.bz2
>
>> is
>> updated as well.
>>
>> Thanks,
>> vs
>>
>
> [PATCH]
>
> Hi!
>
> And thanks again! I took the updated .bz2 from namesys. And I tested the
> poweroff with running vmware. Before that I changed back my lilo.conf to
> read-only mount the root partition. It works!
>
> My /var/log/boot.msg shows the following during next bootup:
>
> <4>reiserfs: checking transaction log (device 03:07) ...
> <4>Warning, log replay starting on readonly filesystem
> <4>reiserfs: replayed 19 transactions in 3 seconds
> <4>Removing [25349 39257 0x0 SD]..<4>done
> <4>Removing [25349 7437 0x0 SD]..<4>done
> <4>Removing [25349 7357 0x0 SD]..<4>done
> <4>There were 3 uncompleted unlinks/truncates. Completed
> <4>Using r5 hash to sort names
> <4>ReiserFS version 3.6.25
> <4>VFS: Mounted root (reiserfs filesystem) readonly.
>
> Yes, and disk space is freed.
>
> Thank you!
>
> Manuel
>
The first time vmware accesses the disk after this reboot my
/var/log/messages shows a line:
Jul 30 17:41:22 firehead kernel: vs-: reiserfs_get_block: [25349 39253
0x80bd001 UNKNOWN] should not be found<7>
After another reboot it doesn't show up any more when running vmware.
I hope this won't cause problems?
Thanks,
Manuel
