Reiser4 and loop device problems

Reiser4 and loop device problems

[Thomas Kuther]

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

Hi,

in recent reiser4 it is not possible to loopback mount a file located
on a reiser4 partition

* kernel 2.6.24-rc2-git5
* reiser4progs 1.0.6
* reiser4 from 2.6.24-rc2-mm1with following series

	sync_sb_inodes-propagate-errors.patch
	reiser4-sb_sync_inodes.patch
	reiser4-export-remove_from_page_cache.patch
	reiser4-export-find_get_pages.patch
	make-copy_from_user_inatomic-not-zero-the-tail-on-i386-vs-reiser4.patch
	reiser4.patch
	jens-broke-reiser4patch-added-to-mm-tree.patch

* filsystem created with
	$ mkfs.reiser4
* mounted with noatime
* no cryptcompress or anything non-default

$ mount -o loop -t iso9660 /tmp/systemrescuecd-x86-0.4.0.iso /mnt/cdrom 
ioctl: LOOP_SET_FD: Invalid argument

Regards,
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Reiser4 and loop device problems

[Dushan Tcholich]

Can you remember the last kernel that worked?

Thanks

Dushan

On Nov 15, 2007 10:44 PM, Thomas Kuther <gimpel@sonnenkinder.org> wrote:
> Hi,
>
> in recent reiser4 it is not possible to loopback mount a file located
> on a reiser4 partition
>
> * kernel 2.6.24-rc2-git5
> * reiser4progs 1.0.6
> * reiser4 from 2.6.24-rc2-mm1with following series
>
>         sync_sb_inodes-propagate-errors.patch
>         reiser4-sb_sync_inodes.patch
>         reiser4-export-remove_from_page_cache.patch
>         reiser4-export-find_get_pages.patch
>         make-copy_from_user_inatomic-not-zero-the-tail-on-i386-vs-reiser4.patch
>         reiser4.patch
>         jens-broke-reiser4patch-added-to-mm-tree.patch
>
> * filsystem created with
>         $ mkfs.reiser4
> * mounted with noatime
> * no cryptcompress or anything non-default
>
> $ mount -o loop -t iso9660 /tmp/systemrescuecd-x86-0.4.0.iso /mnt/cdrom
> ioctl: LOOP_SET_FD: Invalid argument
>
> Regards,
> Tom
>

Re: Reiser4 and loop device problems

[Thomas Kuther]

[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]

On Do, 15.11.07 22:49 "Dushan Tcholich" <dusanc@gmail.com> wrote:

> Can you remember the last kernel that worked?
> 
> Thanks
>
> Dushan

Unfortunately not for sure. I'm not even sure if it ever worked at all,
to be honest. There were some old threads from 2003 saying that loop is
not supported (yet). Did that ever change?

Regards,
Tom

 
> On Nov 15, 2007 10:44 PM, Thomas Kuther <gimpel@sonnenkinder.org>
> wrote:
> > Hi,
> >
> > in recent reiser4 it is not possible to loopback mount a file
> > located on a reiser4 partition
> >
> > * kernel 2.6.24-rc2-git5
> > * reiser4progs 1.0.6
> > * reiser4 from 2.6.24-rc2-mm1with following series
> >
> >         sync_sb_inodes-propagate-errors.patch
> >         reiser4-sb_sync_inodes.patch
> >         reiser4-export-remove_from_page_cache.patch
> >         reiser4-export-find_get_pages.patch
> >         make-copy_from_user_inatomic-not-zero-the-tail-on-i386-vs-reiser4.patch
> >         reiser4.patch
> >         jens-broke-reiser4patch-added-to-mm-tree.patch
> >
> > * filsystem created with
> >         $ mkfs.reiser4
> > * mounted with noatime
> > * no cryptcompress or anything non-default
> >
> > $ mount -o loop -t
> > iso9660 /tmp/systemrescuecd-x86-0.4.0.iso /mnt/cdrom ioctl:
> > LOOP_SET_FD: Invalid argument
> >
> > Regards,
> > Tom
> >

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Reiser4 and loop device problems

[Thomas Kuther]

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

On Fr, 16.11.07 12:02 "Christopher Sawtell" <csawtell@gmail.com> wrote:

> > > Can you remember the last kernel that worked?
> > >
> > > Thanks
> > >
> > > Dushan
> >
> > Unfortunately not for sure. I'm not even sure if it ever worked at
> > all, to be honest. There were some old threads from 2003 saying
> > that loop is not supported (yet). Did that ever change?
> 
> Yes.
> 
> imogen ~ # uname -r
> 2.6.22.9
> imogen ~ # cd /media/Isos/Debian/
> imogen Debian # mount -o loop -t iso9660
> Debian-Etch-4.0-r1-Binary-1-20070819.iso /mnt/tmp
> imogen Debian # ls /mnt/tmp
> README.html          README.txt   debian  install      md5sum.txt
> tools README.mirrors.html  autorun.bat  dists   install.386  pics
> README.mirrors.txt   autorun.inf  doc     isolinux     pool
> 
> But it's broken for linux-2.6.23.1
> 
> If I can be of any further assistance, please do not hesitate to ask.
> 

So which version of reiser4 patch, progs etc do you use?

Edward wrote, it never did. Now.. WTF? :)

Regards,
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Reiser4 and loop device problems

[Thomas Kuther]

[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]

On Do, 15.11.07 18:25 "Joe Feise" <jfeise@feise.com> wrote:

> On Thu, November 15, 2007 15:27, Thomas Kuther wrote:
> > On Fr, 16.11.07 12:02 "Christopher Sawtell" <csawtell@gmail.com>
> > wrote:
> >
> >> > > Can you remember the last kernel that worked?
> >> > >
> >> > > Thanks
> >> > >
> >> > > Dushan
> >> >
> >> > Unfortunately not for sure. I'm not even sure if it ever worked
> >> > at all, to be honest. There were some old threads from 2003
> >> > saying that loop is not supported (yet). Did that ever change?
> >>
> >> Yes.
> >>
> >> imogen ~ # uname -r
> >> 2.6.22.9
> >> imogen ~ # cd /media/Isos/Debian/
> >> imogen Debian # mount -o loop -t iso9660
> >> Debian-Etch-4.0-r1-Binary-1-20070819.iso /mnt/tmp
> >> imogen Debian # ls /mnt/tmp
> >> README.html          README.txt   debian  install      md5sum.txt
> >> tools README.mirrors.html  autorun.bat  dists   install.386  pics
> >> README.mirrors.txt   autorun.inf  doc     isolinux     pool
> >>
> >> But it's broken for linux-2.6.23.1
> >>
> >> If I can be of any further assistance, please do not hesitate to
> >> ask.
> >>
> >
> > So which version of reiser4 patch, progs etc do you use?
> >
> > Edward wrote, it never did. Now.. WTF? :)
> 
> Works here as well on 2.6.22.6:
> joe: mkdir mnt
> joe: sudo mount -o loop -t iso9660 KnoppMythR5F27.iso mnt
> joe: ls -l mnt
> total 10
> dr-xr-xr-x  3 root   root   2048 Sep  8 19:39 KNOPPIX/
> dr-xr-xr-x  3 root   root   2048 May 29  2006 boot/
> 
> Vanilla kernel with reiser4-for-2.6.22-2.patch.gz and
> reiser4progs-1.0.6.tar.gz
> 
> -Joe
> 

Jup, I also tested a plain .22 with namesys patch, and it works
fine. Didn't test with cryptcompress though.

So it seems that something between .22 and .23 broke it again.
Thanks for helping to answer Dushan's question :)

Regards,
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Reiser4 and loop device problems

[Edward Shishkin]

> On Do, 15.11.07 22:49 "Dushan Tcholich" <dusanc@gmail.com> wrote:
>
> > Can you remember the last kernel that worked?
> >
> > Thanks
> >
> > Dushan
>
> Unfortunately not for sure. I'm not even sure if it ever worked at all,
> to be honest. There were some old threads from 2003 saying that loop is
> not supported (yet). Did that ever change?

No, it didn't.
Sorry..

Edward.

>
> Regards,
> Tom
>
>
> > On Nov 15, 2007 10:44 PM, Thomas Kuther <gimpel@sonnenkinder.org>
> > wrote:
> > > Hi,
> > >
> > > in recent reiser4 it is not possible to loopback mount a file
> > > located on a reiser4 partition
> > >
> > > * kernel 2.6.24-rc2-git5
> > > * reiser4progs 1.0.6
> > > * reiser4 from 2.6.24-rc2-mm1with following series
> > >
> > >         sync_sb_inodes-propagate-errors.patch
> > >         reiser4-sb_sync_inodes.patch
> > >         reiser4-export-remove_from_page_cache.patch
> > >         reiser4-export-find_get_pages.patch
> > >         make-copy_from_user_inatomic-not-zero-the-tail-on-i386-vs-reiser4.patch
> > >         reiser4.patch
> > >         jens-broke-reiser4patch-added-to-mm-tree.patch
> > >
> > > * filsystem created with
> > >         $ mkfs.reiser4
> > > * mounted with noatime
> > > * no cryptcompress or anything non-default
> > >
> > > $ mount -o loop -t
> > > iso9660 /tmp/systemrescuecd-x86-0.4.0.iso /mnt/cdrom ioctl:
> > > LOOP_SET_FD: Invalid argument
> > >
> > > Regards,
> > > Tom
> > >
>

Re: Reiser4 and loop device problems

[Arend Freije]

Edward Shishkin wrote:
>> On Do, 15.11.07 22:49 "Dushan Tcholich" <dusanc@gmail.com> wrote:
>>
>>     
>>> Can you remember the last kernel that worked?
>>>
>>> Thanks
>>>
>>> Dushan
>>>       
>> Unfortunately not for sure. I'm not even sure if it ever worked at all,
>> to be honest. There were some old threads from 2003 saying that loop is
>> not supported (yet). Did that ever change?
>>     
>
> No, it didn't.
> Sorry..
>   
>>
>>> On Nov 15, 2007 10:44 PM, Thomas Kuther <gimpel@sonnenkinder.org>
>>> wrote:
>>>       
>>>> ...
>>>> * filsystem created with
>>>>         $ mkfs.reiser4
>>>> * mounted with noatime
>>>> * no cryptcompress or anything non-default
>>>>
>>>> $ mount -o loop -t
>>>> iso9660 /tmp/systemrescuecd-x86-0.4.0.iso /mnt/cdrom ioctl:
>>>> LOOP_SET_FD: Invalid argument
>>>>
>>>>         

Hi,

Sorry for intruding, but I'm a bit surprised about the conformation on
'loop is not supported (yet)' question.
The example of Thomas shows the mounting of an ISO-9960 file system via
a loop device. All partions on my system are reiser4, and I can execute
'mount -t iso9960 -o loop' without any problem. Why do you confirm that
loop is still not supported?

Kind Regards,

Arend Freije

Re: Reiser4 and loop device problems

[Edward Shishkin]

On 11/16/07, Arend Freije <afreije@inn.nl> wrote:
> Edward Shishkin wrote:
> >> On Do, 15.11.07 22:49 "Dushan Tcholich" <dusanc@gmail.com> wrote:
> >>
> >>
> >>> Can you remember the last kernel that worked?
> >>>
> >>> Thanks
> >>>
> >>> Dushan
> >>>
> >> Unfortunately not for sure. I'm not even sure if it ever worked at all,
> >> to be honest. There were some old threads from 2003 saying that loop is
> >> not supported (yet). Did that ever change?
> >>
> >
> > No, it didn't.
> > Sorry..
> >
> >>
> >>> On Nov 15, 2007 10:44 PM, Thomas Kuther <gimpel@sonnenkinder.org>
> >>> wrote:
> >>>
> >>>> ...
> >>>> * filsystem created with
> >>>>         $ mkfs.reiser4
> >>>> * mounted with noatime
> >>>> * no cryptcompress or anything non-default
> >>>>
> >>>> $ mount -o loop -t
> >>>> iso9660 /tmp/systemrescuecd-x86-0.4.0.iso /mnt/cdrom ioctl:
> >>>> LOOP_SET_FD: Invalid argument
> >>>>
> >>>>
>
> Hi,
>

Hello

> Sorry for intruding, but I'm a bit surprised about the conformation on
> 'loop is not supported (yet)' question.
> The example of Thomas shows the mounting of an ISO-9960 file system via
> a loop device. All partions on my system are reiser4, and I can execute
> 'mount -t iso9960 -o loop' without any problem. Why do you confirm that
> loop is still not supported?
>

I tested it a long time ago and there were stall problems.
Since nobody looked at this for a long time, I think, it would be better
for this to be disabled..

Thanks,
Edward.

Re: Reiser4 and loop device problems

[Edward Shishkin]

On 11/16/07, Arend Freije <afreije@inn.nl> wrote:
>
>  Edward Shishkin wrote:
>  On 11/16/07, Arend Freije <afreije@inn.nl> wrote:
>
>
>  Edward Shishkin wrote:
>
>
>
>  On Do, 15.11.07 22:49 "Dushan Tcholich" <dusanc@gmail.com> wrote:
>
>
>
>
>  Can you remember the last kernel that worked?
>
> Thanks
>
> Dushan
>
>
>  Unfortunately not for sure. I'm not even sure if it ever worked at all,
> to be honest. There were some old threads from 2003 saying that loop is
> not supported (yet). Did that ever change?
>
>
>  No, it didn't.
> Sorry..
>
>
>
>
>  On Nov 15, 2007 10:44 PM, Thomas Kuther <gimpel@sonnenkinder.org>
> wrote:
>
>
>
>  ...
> * filsystem created with
>  $ mkfs.reiser4
> * mounted with noatime
> * no cryptcompress or anything non-default
>
> $ mount -o loop -t
> iso9660 /tmp/systemrescuecd-x86-0.4.0.iso /mnt/cdrom ioctl:
> LOOP_SET_FD: Invalid argument
>
>
>
>  Hi,
>
>
>  Hello
>
>
>
>  Sorry for intruding, but I'm a bit surprised about the conformation on
> 'loop is not supported (yet)' question.
> The example of Thomas shows the mounting of an ISO-9960 file system via
> a loop device. All partions on my system are reiser4, and I can execute
> 'mount -t iso9960 -o loop' without any problem. Why do you confirm that
> loop is still not supported?
>
>
>  I tested it a long time ago and there were stall problems.
> Since nobody looked at this for a long time, I think, it would be better
> for this to be disabled..
>  Hi Edward,
>
>  Thanks for your reply. Just to be sure: do you want to disable mounting
> loop devices created with a file containing an image of a Reiser4 file
> system, or do you want to disable mounting loop devices (of any type) on top
> of a already mounted Reiser4 file system?
>

Loop devices created over reiser4 files don't work properly.
Do not try to use them for now.

Thanks,
Edward.

Re: Reiser4 and loop device problems

[Edward Shishkin]

On 11/16/07, Edward Shishkin <edward.shishkin@gmail.com> wrote:
> On 11/16/07, Arend Freije <afreije@inn.nl> wrote:
> >
> >  Edward Shishkin wrote:
> >  On 11/16/07, Arend Freije <afreije@inn.nl> wrote:
> >
> >
> >  Edward Shishkin wrote:
> >
> >
> >
> >  On Do, 15.11.07 22:49 "Dushan Tcholich" <dusanc@gmail.com> wrote:
> >
> >
> >
> >
> >  Can you remember the last kernel that worked?
> >
> > Thanks
> >
> > Dushan
> >
> >
> >  Unfortunately not for sure. I'm not even sure if it ever worked at all,
> > to be honest. There were some old threads from 2003 saying that loop is
> > not supported (yet). Did that ever change?
> >
> >
> >  No, it didn't.
> > Sorry..
> >
> >
> >
> >
> >  On Nov 15, 2007 10:44 PM, Thomas Kuther <gimpel@sonnenkinder.org>
> > wrote:
> >
> >
> >
> >  ...
> > * filsystem created with
> >  $ mkfs.reiser4
> > * mounted with noatime
> > * no cryptcompress or anything non-default
> >
> > $ mount -o loop -t
> > iso9660 /tmp/systemrescuecd-x86-0.4.0.iso /mnt/cdrom ioctl:
> > LOOP_SET_FD: Invalid argument
> >
> >
> >
> >  Hi,
> >
> >
> >  Hello
> >
> >
> >
> >  Sorry for intruding, but I'm a bit surprised about the conformation on
> > 'loop is not supported (yet)' question.
> > The example of Thomas shows the mounting of an ISO-9960 file system via
> > a loop device. All partions on my system are reiser4, and I can execute
> > 'mount -t iso9960 -o loop' without any problem. Why do you confirm that
> > loop is still not supported?
> >
> >
> >  I tested it a long time ago and there were stall problems.
> > Since nobody looked at this for a long time, I think, it would be better
> > for this to be disabled..
> >  Hi Edward,
> >
> >  Thanks for your reply. Just to be sure: do you want to disable mounting
> > loop devices created with a file containing an image of a Reiser4 file
> > system, or do you want to disable mounting loop devices (of any type) on top
> > of a already mounted Reiser4 file system?
> >
>
> Loop devices created over reiser4 files don't work properly.
> Do not try to use them for now.
>

Well, I have restored loopback functionality, and loop devices
over files managed by default file plugin seems to be working
in the latest -mm and reiser4-for-2.6.23.

Thanks,
Edward.

> Thanks,
> Edward.
>

Re: Reiser4 and loop device problems

[Thomas Kuther]

[-- Attachment #1.1: Type: text/plain, Size: 2284 bytes --]

FWD to list.

On 11/16/07, Thomas Kuther <gimpel@sonnenkinder.org> wrote:
> On Fr, 16.11.07 12:02 "Christopher Sawtell" <csawtell@gmail.com>
> wrote:
>
> > > > Can you remember the last kernel that worked?
> > > >
> > > > Thanks
> > > >
> > > > Dushan
> > >
> > > Unfortunately not for sure. I'm not even sure if it ever worked at
> > > all, to be honest. There were some old threads from 2003 saying
> > > that loop is not supported (yet). Did that ever change?
> >
> > Yes.
> >
> > imogen ~ # uname -r
> > 2.6.22.9
> > imogen ~ # cd /media/Isos/Debian/
> > imogen Debian # mount -o loop -t iso9660
> > Debian-Etch-4.0-r1-Binary-1-20070819.iso /mnt/tmp
> > imogen Debian # ls /mnt/tmp
> > README.html          README.txt   debian  install      md5sum.txt
> > tools README.mirrors.html  autorun.bat  dists   install.386  pics
> > README.mirrors.txt   autorun.inf  doc     isolinux     pool
> >
> > But it's broken for linux-2.6.23.1
> >
> > If I can be of any further assistance, please do not hesitate to
> > ask.
> >
>
> So which version of reiser4 patch, progs etc do you use?
>
> Edward wrote, it never did. Now.. WTF? :)

Odd isn't it, but the attached log is a pretty convincing
demonstration to me, and it will mount .iso files fine too. Somebody
must have corrected what turned out to be a tiny bug and never
documented it.

However you cannot fsck.reiser4 the filesystem in the file:-
imogen tester # fsck.reiser4 --check opt.img
Fatal: The partition (opt.img) is mounted with write permissions,
cannot fsck it.
imho that should be fixed sometime.

The patch against 2.6.22.9 is reiser4-for-2.6.22-2.patch.gz
       size: 619987
md5sum: f7060338c6b3f59a8b6aeee59e15f7a5

The patch against linux-2.6.23.1 is reiser4-for-2.6.23.patch.bz2
      size: 447704
md5sum: 818328d0e50fc90f05832e680562dd4a

( Just so we all know exactly what I'm doing :-)

The utility programs are reiser4progs-1.0.6.tar.gz
      size: 799613

btw, There was a bug which showed up if you tried to over fill the
file system using either bittorrent or rsync. The filesystem used to
get seriously discombobulated. I haven't been game to try to trigger
it recently.

Has that been been fixed?

-- 
Sincerely etc.
Christopher Sawtell

[-- Attachment #1.2: showit --]
[-- Type: text/plain, Size: 1441 bytes --]

imogen media # mkdir tester
imogen media # cd $_
imogen tester # dd if=/dev/hda8 of=opt.img
4883697+0 records in
4883697+0 records out
2500452864 bytes (2.5 GB) copied, 185.435 s, 13.5 MB/s
imogen tester # mount
/dev/hda3 on / type ext2 (rw,noatime)
proc on /proc type proc (rw,nosuid,nodev,noexec)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec)
udev on /dev type tmpfs (rw,nosuid)
devpts on /dev/pts type devpts (rw,nosuid,noexec)
/dev/hda5 on /usr type reiser4 (rw)
/dev/hda6 on /home type reiser4 (rw)
/dev/hda7 on /var type reiser4 (rw)
/dev/hda8 on /opt type reiser4 (rw)
/dev/hda9 on /media type reiser4 (rw)
shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85)
nfsd on /proc/fs/nfs type nfsd (rw,noexec,nosuid,nodev)
/dev/hda1 on /boot type ext2 (rw,noatime)
imogen tester # mount -o loop -t reiser4 opt.img /mnt/tmp
imogen tester # ls -l /mnt/tmp/
total 6
drwxr-xr-x 4 root root  5 Aug 12 19:34 Acrobat7
drwxr-xr-x 9 root root 11 Aug 28 18:30 RealPlayer
drwxr-xr-x 2 root root 13 Dec 19  2003 adobesvg-3.01
drwxr-xr-x 2 root root  3 Aug 12 19:34 bin
drwxr-xr-x 2 root root  2 Oct 11 22:18 lost+found
drwxr-xr-x 4 root root  4 Aug  8 01:30 netscape
drwxr-xr-x 7 root root  8 Sep 22 11:20 sun-jdk-1.5.0.12
drwxr-xr-x 7 root root  8 Oct  4 23:29 sun-jdk-1.6.0.03
drwxr-xr-x 8 root root  8 Oct 16 02:03 sun-jre-bin-1.6.0.03


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: Reiser4 and loop device problems

[Thomas Kuther]

[-- Attachment #1: Type: text/plain, Size: 2622 bytes --]


Silly me had the file mounted - forget I mentioned that one could not
fsck reiser4 files.
My apologies.


On 11/16/07, Christopher Sawtell <csawtell@gmail.com> wrote:
> On 11/16/07, Thomas Kuther <gimpel@sonnenkinder.org> wrote:
> > On Fr, 16.11.07 12:02 "Christopher Sawtell" <csawtell@gmail.com>
> > wrote:
> >
> > > > > Can you remember the last kernel that worked?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Dushan
> > > >
> > > > Unfortunately not for sure. I'm not even sure if it ever worked
> > > > at all, to be honest. There were some old threads from 2003
> > > > saying that loop is not supported (yet). Did that ever change?
> > >
> > > Yes.
> > >
> > > imogen ~ # uname -r
> > > 2.6.22.9
> > > imogen ~ # cd /media/Isos/Debian/
> > > imogen Debian # mount -o loop -t iso9660
> > > Debian-Etch-4.0-r1-Binary-1-20070819.iso /mnt/tmp
> > > imogen Debian # ls /mnt/tmp
> > > README.html          README.txt   debian  install      md5sum.txt
> > > tools README.mirrors.html  autorun.bat  dists   install.386  pics
> > > README.mirrors.txt   autorun.inf  doc     isolinux     pool
> > >
> > > But it's broken for linux-2.6.23.1
> > >
> > > If I can be of any further assistance, please do not hesitate to
> > > ask.
> > >
> >
> > So which version of reiser4 patch, progs etc do you use?
> >
> > Edward wrote, it never did. Now.. WTF? :)
>
> Odd isn't it, but the attached log is a pretty convincing
> demonstration to me, and it will mount .iso files fine too. Somebody
> must have corrected what turned out to be a tiny bug and never
> documented it.
>
> However you cannot fsck.reiser4 the filesystem in the file:-
> imogen tester # fsck.reiser4 --check opt.img
> Fatal: The partition (opt.img) is mounted with write permissions,
> cannot fsck it.
> imho that should be fixed sometime.
>
> The patch against 2.6.22.9 is reiser4-for-2.6.22-2.patch.gz
>        size: 619987
> md5sum: f7060338c6b3f59a8b6aeee59e15f7a5
>
> The patch against linux-2.6.23.1 is reiser4-for-2.6.23.patch.bz2
>       size: 447704
> md5sum: 818328d0e50fc90f05832e680562dd4a
>
> ( Just so we all know exactly what I'm doing :-)
>
> The utility programs are reiser4progs-1.0.6.tar.gz
>       size: 799613
>
> btw, There was a bug which showed up if you tried to over fill the
> file system using either bittorrent or rsync. The filesystem used to
> get seriously discombobulated. I haven't been game to try to trigger
> it recently.
>
> Has that been been fixed?
>
> --
> Sincerely etc.
> Christopher Sawtell
>


-- 
Sincerely etc.
Christopher Sawtell

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]