From: Alexander Viro <viro@math.psu.edu>
To: abc abc <netlogin_99@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: rename problem on vfat file systems
Date: Thu, 21 Jun 2001 15:12:26 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.21.0106211510400.209-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <20010621190434.82955.qmail@web9604.mail.yahoo.com>
On Thu, 21 Jun 2001, abc abc wrote:
> If I reboot the machine just after the rename() call
> is completed, when the machine comes up the file
> /mnt/sns-c/segments/segfile has zero bytes and there
> is no file in the tmp directory. Effectively the file
> is lost some where. Running fsck recovers the file,
> but it doesn't help me much because I would be copying
> hundreds of files and its difficult to match the
> files.
>
> Can you think of any thing that might be causing this.
Crappy filesystem layout. If you want to do something a-la journalling
for VFAT - seek professional help.
prev parent reply other threads:[~2001-06-21 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 19:04 rename problem on vfat file systems abc abc
2001-06-21 19:12 ` Alexander Viro [this message]
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=Pine.GSO.4.21.0106211510400.209-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netlogin_99@yahoo.com \
/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).