mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Walker <alex@x3ja.co.uk>
To: linux-kernel@vger.kernel.org
Cc: huggie@earth.li
Subject: VFAT problems in 2.4.14
Date: Thu, 15 Nov 2001 01:00:20 +0000	[thread overview]
Message-ID: <20011115010020.B510@x3ja.co.uk> (raw)

[Please CC me in any replies - I am not subscribed to the list]

I was copying some files from a reiserfs partition to a FAT32 partition
with the simple command `sudo cp -a Docs/mywork My\ Documents\Work`.
Where "My\ Documents" is a symlink to a directory on my windows
partition.  I did this as sudo since I had no set up permissions on my
FAT32 partition for my normal user.  I then rebooted into Windows, only
to discover that it had gone badly wrong.

The original directory had only 3 subdirectories.  2 of these
transferred across without any errors.  The final one was created, but
the contents corrupted.  It originally had 1.4M of data in 6 document
files.  Instead of these files, files and directories with spurious
names (lots of symbols I can't type in my editor) were created.

Not only this, but the contents of this directory claimed to total 74G
(on a 20G disk!).  None of the files were readable in Windows.

I rebooted again into linux and investigated some more.
- The files names were all 12 characters long. 
- There are 72 of these files.
- When listing the directories you get "Directory sread (sector
  0xd12a66d, limit 6136798" "attempt to access beyond end of device"
  errrors.
- Again, linux thinks the directory is 72G big (but df disagrees on
  partition size)
- Even though the partition is mounted read-only, any attempt to re-copy
  is met with a "creating `file`: Read-only file system" error

Fortunately it was a copy, not a move!

Hope this is helpful.  Any advice appreciated.

aLeX

-- 
-----------------------------
Alex Walker   alex@x3ja.co.uk 
        x3ja|alex
-----------------------------

                 reply	other threads:[~2001-11-15  1:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20011115010020.B510@x3ja.co.uk \
    --to=alex@x3ja.co.uk \
    --cc=huggie@earth.li \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®