All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend Freije <afreije@inn.nl>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: Thomas Kuther <gimpel@sonnenkinder.org>,
	ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 and loop device problems
Date: Fri, 16 Nov 2007 08:08:26 +0100	[thread overview]
Message-ID: <473D41EA.4020107@inn.nl> (raw)
In-Reply-To: <5c7c368b0711151503p6ae801fcsa3803fbd65443341@mail.gmail.com>

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


  reply	other threads:[~2007-11-16  7:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5c7c368b0711151455l2cf7a080yff21884e5957d20b@mail.gmail.com>
2007-11-15 23:03 ` Reiser4 and loop device problems Edward Shishkin
2007-11-16  7:08   ` Arend Freije [this message]
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-16  9:15 Thomas Kuther
  -- strict thread matches above, loose matches on Subject: below --
2007-11-16  9:14 Thomas Kuther
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=473D41EA.4020107@inn.nl \
    --to=afreije@inn.nl \
    --cc=edward.shishkin@gmail.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.