Linux NILFS development
 help / color / mirror / Atom feed
From: robinx99-hi6Y0CQ0nG0@public.gmane.org
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: Kernel Bug after corrupted filesystem
Date: Sat, 03 Jan 2009 08:54:38 +0100	[thread overview]
Message-ID: <20090103075438.264510@gmx.net> (raw)
In-Reply-To: <20090102.002735.88475791.ryusuke-sG5X7nlA6pw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]

Oops didn't send the mail to the mailinglist, so I will resend.
Hi
> 
> Thanks for your help.
> I have another request:
> 
>  # dumpseg /dev/loop1 12

root@robin-laptop:/tmp# dumpseg /dev/loop1 12
segment: segnum = 12
  partial segment
    creation time = 2008-12-26 11:45:06
    nfinfo = 0



> 
>  - This will dump the summary of the segment in question
> 
>  # dd if=/dev/loop1 bs=4k skip=24576 count=2 | hd
> 
>  - This will dump the (broken) root block of the file system
> 
Ok I atached it to the email bzip2 compressed
> According to your log, the btree root of DAT file (i.e. a table file
> to translate disk addresses) seems inconsistent.  It might not be
> updated properly when GC moved its blocks.  I suspect that it was
> caused by some sort of GC problem.
> 
> And, your nilfs partition seems to have shut down uncleanly before
> this mount error repeatedly happened.  Do you remember what the first
> trouble was like?
> 
Actualy I have no real idea. Didn't start the computer for some days over christmas, befor christmas I could use the filesystem withoul any trouble, and on december 26 I was unable to mount it.
I actualy quite often moved files of the nilfs filesystem to an USB stick. Using comands like 
"mv /mnt/nilfs/directory/*.avi /mnt/usb && poweroff". So there were some shutdowns I didn't watch, and I was thinking that the normal shutdown scripts should unmount every mounted filesystem. Well the computer was definitv off, but I have no idea if it could be possible that something importend was stoped to soon when it came to the point "sending all procecess the term signal"

> Regards,
> Ryusuke
> 
robinx99

[-- Attachment #2: hd.bz2 --]
[-- Type: application/octet-stream, Size: 4095 bytes --]

[-- Attachment #3: Type: text/plain, Size: 158 bytes --]

_______________________________________________
users mailing list
users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
https://www.nilfs.org/mailman/listinfo/users

  parent reply	other threads:[~2009-01-03  7:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30 13:19 Kernel Bug after corrupted filesystem robinx99-hi6Y0CQ0nG0
     [not found] ` <20081230131953.298540-hi6Y0CQ0nG0@public.gmane.org>
2008-12-31  2:53   ` Ryusuke Konishi
     [not found]     ` <20081231.115354.105606600.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-12-31  3:12       ` Ryusuke Konishi
2008-12-31 11:17       ` Dennis Peiler
     [not found]         ` <20081231111707.25420-hi6Y0CQ0nG0@public.gmane.org>
2008-12-31 14:36           ` Ryusuke Konishi
     [not found]             ` <20081231.233620.76970897.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-01-01  8:34               ` dennis-peiler-hi6Y0CQ0nG0
2009-01-01  9:31               ` robinx99-hi6Y0CQ0nG0
     [not found]                 ` <20090101093121.302730-hi6Y0CQ0nG0@public.gmane.org>
2009-01-01 15:27                   ` Ryusuke Konishi
     [not found]                     ` <20090102.002735.88475791.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-01-03  7:54                       ` robinx99-hi6Y0CQ0nG0 [this message]
     [not found]                         ` <20090103075438.264510-hi6Y0CQ0nG0@public.gmane.org>
2009-01-03 16:10                           ` Ryusuke Konishi

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=20090103075438.264510@gmx.net \
    --to=robinx99-hi6y0cq0ng0@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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