On Tue, Nov 21, 2006 at 11:20:42PM -0500, [EMAIL PROTECTED] wrote:
> On Tue, Nov 21, 2006 at 10:37:27PM -0500, Douglas Tutty wrote:
> >
> > I went from ext3 to reiserfs because ext3 didn't stand up long term to
> > power failures (then from reiserfs to jfs when it became available).
>
> Well, if
On Tue, Nov 21, 2006 at 10:37:27PM -0500, Douglas Tutty wrote:
> On Tue, Nov 21, 2006 at 09:53:41PM -0500, [EMAIL PROTECTED] wrote:
> > On Tue, Nov 21, 2006 at 10:38:45AM -0500, Douglas Tutty wrote:
> >
> > > So I use JFS for everything.
> > >
> >
> > I'm at the point of replacing one of my rei
On Tue, Nov 21, 2006 at 10:37:27PM -0500, Douglas Tutty wrote:
>
> I went from ext3 to reiserfs because ext3 didn't stand up long term to
> power failures (then from reiserfs to jfs when it became available).
Well, if that's the situation, going form reiserfs to ext3 fs doesn't
seem like that mu
On Tue, Nov 21, 2006 at 09:53:41PM -0500, [EMAIL PROTECTED] wrote:
> On Tue, Nov 21, 2006 at 10:38:45AM -0500, Douglas Tutty wrote:
>
> > So I use JFS for everything.
> >
>
> I'm at the point of replacing one of my reiserfs's on an NFS server with
> something else for reliability. (reliabilit
On Mon, Nov 20, 2006 at 09:52:26PM -0500, [EMAIL PROTECTED] wrote:
> On Mon, Nov 20, 2006 at 06:43:06PM -0500, Johan Kullstam wrote:
> >
> > I have recently switched from reiserfs to jfs
>
> > So far so good, but then again, I was largely happy with reiserfs over
> > the past 4 or so years.
On Tue, Nov 21, 2006 at 10:38:45AM -0500, Douglas Tutty wrote:
> On Mon, Nov 20, 2006 at 09:52:26PM -0500, [EMAIL PROTECTED] wrote:
> > On Mon, Nov 20, 2006 at 06:43:06PM -0500, Johan Kullstam wrote:
> >
> > >From what I hear, reiserfs and ext3 are both reasonably protected
> > against panic rebo
On 2006-11-16 @ 19:28:40 (week 46) Douglas Tutty wrote:
> I see from later posts that reiserfsck worked. I used to have this
> problem. I tracked it down to a problem within reiserfs where it stores
> small files within the directory structure itself (as a speed-up
> measure). I got tired of it
On Thu, Nov 16, 2006 at 05:03:22PM +, J.A. de Vries wrote:
> On 2006-11-16 @ 08:56:14 (week 46) [EMAIL PROTECTED] wrote:
>
> > Rumours I have heard about reiserfsck suggest to me that taking a backup
> > is *highly* recommended before doing reiserfsck.
>
> Right you are! I did, excluding the
On Wed, Nov 15, 2006 at 03:02:23PM +, J.A. de Vries wrote:
> Hi,
>
> I have a problem with a file which seems to not exist, but that makes
> applications like rsync, offlineimap and tar crash, because they try to read
> it
> anyway (not their fault as far as I can tell).
>
> When I try to sy
On Thu, Nov 16, 2006 at 11:21:40AM -0600, John Hasler wrote:
> hendrik writes:
> > I thought that a deleted file that was still being read *was* unlinked
> > from the directory, just not removed from the disk until it was closed.
>
> The directory entry is deleted and the link count is decremented
On 2006-11-16 @ 10:42:25 (week 46) Bob McGowan wrote:
> First, HdV has discovered his problem is directory structure corruption.
> This is the correct answer, based on all the failed attempts to
> remove, in one way or another, this file.
Indeed. What most of the proposed methods had in common
John Hasler wrote:
hendrik writes:
I thought that a deleted file that was still being read *was* unlinked
from the directory, just not removed from the disk until it was closed.
The directory entry is deleted and the link count is decremented when the
file is deleted from the directory. When
You might try emacs on the directory: emacs .
This brings up dired mode where you can hit "d" on the file(s) you don't
want
and "x" to execute your instructions.
David Gluss
408 866 4125 x307
hendrik writes:
> I thought that a deleted file that was still being read *was* unlinked
> from the directory, just not removed from the disk until it was closed.
The directory entry is deleted and the link count is decremented when the
file is deleted from the directory. When the file was opened
On 2006-11-16 @ 08:56:14 (week 46) [EMAIL PROTECTED] wrote:
> Rumours I have heard about reiserfsck suggest to me that taking a backup
> is *highly* recommended before doing reiserfsck.
Right you are! I did, excluding the directory containing the troublesome
file.
> Some copying/backup programs
On Thu, Nov 16, 2006 at 08:19:55AM -0600, Mike McCarty wrote:
> [EMAIL PROTECTED] wrote:
> >On Thu, Nov 16, 2006 at 10:14:00AM +, J.A. de Vries wrote:
> >
> >>On 2006-11-15 @ 22:27:03 (week 46) Mike McCarty wrote:
> >>
> >>
> >>>OTOH, something is there. Try using
> >>>
> >>># lsof
> >>
> >>Ah,
On Thu, Nov 16, 2006 at 10:00:31AM +, J.A. de Vries wrote:
> On 2006-11-15 @ 19:16:00 (week 46) Wayne Topa wrote:
>
> > Been there, done that. Now when I come across a file the is there but
> > isn't, I run mc. If it's really there, mc will remove it.
>
> Hi Wayne,
>
> Well then, that conv
[EMAIL PROTECTED] wrote:
On Thu, Nov 16, 2006 at 10:14:00AM +, J.A. de Vries wrote:
On 2006-11-15 @ 22:27:03 (week 46) Mike McCarty wrote:
OTOH, something is there. Try using
# lsof
Ah, hadn't thought of lsof or fuser yet. Good reminder, thanks!
I tried both but lsof didn't list the
On Thu, Nov 16, 2006 at 10:14:00AM +, J.A. de Vries wrote:
>
> I am gonna do one more thing (looking in /proc for any references to
> that file). But at the moment I think that maybe this is some corruption
> in the filesystem (ReiserFS). In that case running reiserfsck might
> help. I am hopi
On Thu, Nov 16, 2006 at 10:14:00AM +, J.A. de Vries wrote:
> On 2006-11-15 @ 22:27:03 (week 46) Mike McCarty wrote:
>
> > OTOH, something is there. Try using
> >
> > # lsof
>
> Ah, hadn't thought of lsof or fuser yet. Good reminder, thanks!
>
> I tried both but lsof didn't list the file as
On 2006-11-15 @ 22:27:03 (week 46) Mike McCarty wrote:
> OTOH, something is there. Try using
>
> # lsof
Ah, hadn't thought of lsof or fuser yet. Good reminder, thanks!
I tried both but lsof didn't list the file as being used and fuser
couldn't find the file at all ("No such file or directory").
On 2006-11-15 @ 19:16:00 (week 46) Wayne Topa wrote:
> Been there, done that. Now when I come across a file the is there but
> isn't, I run mc. If it's really there, mc will remove it.
Hi Wayne,
Well then, that convinced me the problem is to be found at a lower
level. mc listed the file with a
On 2006-11-15 @ 17:47:40 (week 46) Greg Folkert wrote:
> On Wed, 2006-11-15 at 15:02 +, J.A. de Vries wrote:
> [...snip...]
> > #---
> > # cd ~/Maildir/.Applications.\[vim\]/cur
> > # ls 1141914051.*
> > ls:
> > 11419
On 15 Nov 2006, Wayne Topa wrote:
> J.A. de Vries([EMAIL PROTECTED]) is reported to have said:
> > Hi,
> > To be honest I don't know what to do next. I really want to backup my mail,
> > but cannot because of this problem. To solve the problem I need to remove
> > the
> > file, but when I do try s
Ken Irving wrote:
On Wed, Nov 15, 2006 at 08:54:15PM +, J.A. de Vries wrote:
On 2006-11-15 @ 11:20:46 (week 46) Ralph Katz wrote:
How about:
# rm -f 1141914051.*
No promises... but something like that worked once for me in a similar
mysterious situation.
Ah, hadn't tried that yet. T
# rm -f 1141914051.*
No promises... but something like that worked once for me in a similar
mysterious situation.
Ah, hadn't tried that yet. Too bad it didn't work.
$ rm -i 1141914051.*
rm: cannot lstat
`1141914051.M484859P8695V0309Ip0007553_0.draupnir,S=3707:2,S':
No such file or
J.A. de Vries([EMAIL PROTECTED]) is reported to have said:
> Hi,
> To be honest I don't know what to do next. I really want to backup my mail,
> but cannot because of this problem. To solve the problem I need to remove the
> file, but when I do try such I get told it isn't there. Any suggestions?
>
On Wed, 2006-11-15 at 15:02 +, J.A. de Vries wrote:
[...snip...]
> #---
> # cd ~/Maildir/.Applications.\[vim\]/cur
> # ls 1141914051.*
> ls: 1141914051.M484859P8695V0309Ip0007553_0.draupnir,S=3707:2,S:
> No
On 2006-11-15 @ 12:25:25 (week 46) Ken Irving wrote:
> See if find sees the file, e.g.,
>
> find -name 11419\*
>
> and if it does, then something like
>
> find -name 11419\* -exec rm {} \;
>
> or
> find -name 11419\* -exec mv {} somename \;
>
> if you'd like to have a look at it.
On 2006-11-15 @ 16:35:28 (week 46) Matthew Krauss wrote:
> I'm thinking you have a file with a name that the shell doesn't want to
> handle correctly.
As far as I can tell, there's nothing irregular about the name itself.
The only somewhat "special" characters in it are a comma, an equal sign
an
J.A. de Vries wrote:
On 2006-11-15 @ 11:20:46 (week 46) Ralph Katz wrote:
How about:
# rm -f 1141914051.*
No promises... but something like that worked once for me in a similar
mysterious situation.
Ah, hadn't tried that yet. Too bad it didn't work.
$ rm -i 1141914051.*
rm: cannot
On Wed, Nov 15, 2006 at 08:54:15PM +, J.A. de Vries wrote:
> On 2006-11-15 @ 11:20:46 (week 46) Ralph Katz wrote:
>
> > How about:
> >
> > # rm -f 1141914051.*
> >
> > No promises... but something like that worked once for me in a similar
> > mysterious situation.
>
> Ah, hadn't tried that
On 2006-11-15 @ 11:20:46 (week 46) Ralph Katz wrote:
> How about:
>
> # rm -f 1141914051.*
>
> No promises... but something like that worked once for me in a similar
> mysterious situation.
Ah, hadn't tried that yet. Too bad it didn't work.
$ rm -i 1141914051.*
rm: cannot lstat
`1141914051.M4
On 11/15/2006 10:10 AM, J.A. de Vries wrote:
> Hi,
>
> I have a problem with a file which seems to not exist, but that makes
> applications like rsync, offlineimap and tar crash, because they try to read
> it
> anyway (not their fault as far as I can tell).
>
> However when I try to find that
34 matches
Mail list logo
