From: Zan Lynx <zlynx@acm.org>
To: ReiserFS Mailing List <reiserfs-devel@vger.kernel.org>
Subject: 2.6.23-rc1-mm2 Invalid argument on some files, depends on file contents?
Date: Wed, 01 Aug 2007 15:57:01 -0600 [thread overview]
Message-ID: <1186005421.9066.9.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
Several of my files have been doing this. I really noticed it when I
ran a backup last night and there were many of these errors. It has
also started affecting documents I really care about.
I was wondering if I somehow have compression enabled. I didn't do it
on purpose! :)
I remember reading some comment about lzo being messed up and the
patches not included in mm yet? This is rc1-mm2 so I thought it might
be fixed, but I guess not.
Here is a snippet of a shell session showing the problem. It's a good
thing it didn't affect the OpenOffice format original!
$ cat * >/dev/null
cat: URL Database Design.doc.backup: Invalid argument
$ cp URL\ Database\ Design.doc.backup{,.test}
$ cat * >/dev/null
cat: URL Database Design.doc.backup: Invalid argument
cat: URL Database Design.doc.backup.test: Invalid argument
$ echo blah >> URL\ Database\ Design.doc.backup.test
$ cat * >/dev/null
cat: URL Database Design.doc.backup: Invalid argument
$ ls -l
-rw-r--r-- 1 lynx users 286720 2007-07-31 18:16 URL Database Design.doc.backup
-rw-r--r-- 1 lynx users 286725 2007-08-01 15:48 URL Database Design.doc.backup.test
-rw-r--r-- 1 lynx users 154915 2007-07-31 16:53 URL Database Design.odt
-rw-r--r-- 1 lynx users 154915 2007-07-31 18:16 URL Database Design.odt.backup
As you can see, a copy shows the same problem. But adding "blah\n" to
the end makes the problem go away...
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-08-01 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 21:57 Zan Lynx [this message]
2007-08-01 23:48 ` 2.6.23-rc1-mm2 Invalid argument on some files, depends on file contents? Edward Shishkin
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=1186005421.9066.9.camel@localhost \
--to=zlynx@acm.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.