reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Kuther <gimpel@sonnenkinder.org>
To: reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4 and loop device problems
Date: Fri, 16 Nov 2007 10:14:43 +0100	[thread overview]
Message-ID: <20071116101443.08b3919e@sirius> (raw)


[-- 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 --]

             reply	other threads:[~2007-11-16  9:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16  9:14 Thomas Kuther [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-16  9:15 Reiser4 and loop device problems Thomas Kuther
     [not found] <5c7c368b0711151455l2cf7a080yff21884e5957d20b@mail.gmail.com>
2007-11-15 23:03 ` Edward Shishkin
2007-11-16  7:08   ` Arend Freije
2007-11-16 10:08     ` Edward Shishkin
     [not found]       ` <473D6EB9.50005@inn.nl>
2007-11-16 11:03         ` Edward Shishkin
2007-12-04 23:39           ` Edward Shishkin
2007-11-15 21:44 Thomas Kuther
2007-11-15 21:51 ` Dushan Tcholich
     [not found] ` <a08621850711151349m6ae91e74led14485dd41c2f8f@mail.gmail.com>
2007-11-15 22:10   ` Thomas Kuther
     [not found]     ` <b8d16a880711151502h509cac93m7453a66b551f4fae@mail.gmail.com>
2007-11-15 23:27       ` Thomas Kuther
     [not found]         ` <45639.76.236.51.34.1195179949.squirrel@scotch.ics.uci.edu>
2007-11-16  9:24           ` Thomas Kuther

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071116101443.08b3919e@sirius \
    --to=gimpel@sonnenkinder.org \
    --cc=reiserfs-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).