From: Anton Altaparmakov <aia21@cantab.net>
To: Nico Schottelius <nico-mutt@schottelius.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Bugs in 2.5.28 [scsi/framebuffer/devfs/floppy/ntfs/trident]
Date: Thu, 01 Aug 2002 14:02:00 +0100 [thread overview]
Message-ID: <5.1.0.14.2.20020801134624.00aabec0@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <20020801115047.GB1577@schottelius.org>
At 12:50 01/08/02, Nico Schottelius wrote:
>Anton Altaparmakov [Tue, Jul 30, 2002 at 05:28:05PM +0100]:
> > I am interested in this ntfs report. Which way round was the loopback
> file?
> > I.e. did you mount: mount -t ntfs -o loop somefile_on_a_non_ntfs_partition
> > or did you mount: mount -t some_file_system -o loop
> > somefile_on_an_ntfs_partion?
>
>mount -t ntfs -o loop file.sav-on-ext2-or-on-xfs[when using 2.4.18] /mnt
>
> > Can you send me the errors produced? If there is an oops, please decode
> and
> > send it, too.
>
>The test I did was the following [may I call that test ?]:
>
>cd /mnt; mkdir /ntfs_on_ext3; cp -r * /ntfs_on_ext3
>While copying, with or without debug, the system hangs, but top only reports
>7 % cpu load.
>
>Copying the files results in a input / output error.
Interesting.
>It has never been an oops and actually 2.5.29 does _not_ hangup anymore!
>Still it stops to copy the files and aborts.
>I am currently retrying with debug enabled...
>
> > Also it may be useful to have the debug output from ntfs (depending on
> what
> > the errors/oops say - they may be sufficient to pinpoint the problem),
> i.e.
> > enable debugging when configuring the kernel, and then as root do: echo
> 1 >
> > /proc/sys/fs/ntfs-debug. Note this will absolutely flood you with debug
> > output so the system will run slow as hell... So it is best to only enable
> > debug messages just before the error occurs if that is possible.
>
>oops. forget that above. Oh yes, ntfs is really reporting much.
>You can find the output at ftp.schottelius.org:/pub/tmp, it's about
>600k compressed.
Where is it? It doesn't appear - I just looked...
>I am really happy that this time the cp did not hald my system!
>
>p.s.: what was the maximal file size on ext3 ? I just gunzipped a 4gb
> file (the ntfs image the whole story is about), which could not
> be transfered through scp/ftp in this size...
Sorry not sure. I think it is dependent on the fs block size you use...
Anton
--
"I've not lost my mind. It's backed up on tape somewhere." - Unknown
--
Anton Altaparmakov <aia21 at cantab.net> (replace at with @)
Linux NTFS Maintainer / IRC: #ntfs on irc.openprojects.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2002-08-01 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 17:57 Nico Schottelius
2002-07-30 16:28 ` Anton Altaparmakov
2002-08-01 11:50 ` Nico Schottelius
2002-08-01 13:02 ` Anton Altaparmakov [this message]
2002-08-02 3:40 ` Nico Schottelius
2002-08-02 3:59 ` Nico Schottelius
2002-08-05 8:58 ` Anton Altaparmakov
2002-07-31 17:22 ` James Simmons
2002-07-31 21:58 ` Nico Schottelius
2002-08-01 21:07 ` James Simmons
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=5.1.0.14.2.20020801134624.00aabec0@pop.cus.cam.ac.uk \
--to=aia21@cantab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nico-mutt@schottelius.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
all inboxes | Powered by JetHome®