public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Dittmer <jdi@l4x.org>
To: Balbir Singh <bsingharora@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, dev@sw.ru, jblunck@suse.de
Subject: Re: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
Date: Wed, 08 Feb 2006 23:42:17 +0100	[thread overview]
Message-ID: <43EA73C9.7010101@l4x.org> (raw)
In-Reply-To: <661de9470602081006p2a3132e8x2436de89e9395748@mail.gmail.com>

Balbir Singh wrote:
>>>>$ umount /mnt/data
>>>>Segmentation Fault
>>>>
>>>>dmesg:
>>>>
>>>>VFS: Busy inodes after unmount. Self-destruct in 5 seconds.  Have a nice day...
>>>>Unable to handle kernel NULL pointer dereference at virtual address 00000034
>>>
>>>
> 
> There were a couple of fixes suggested for the busy inodes afer
> unmount problem. Please see
> 
> http://lkml.org/lkml/2006/1/25/17
> 
> and
> 
> http://lkml.org/lkml/2006/1/30/108
> You could see if any one of them fixes your problem. There is also
> Kirill's fix which was in mm (not sure about it now)

Thanks for the suggestion, but I couldn't reproduce it with a simple
mount/umount and the partition in question is gone for good now. And I
don't feel like risiking 450gb of data, even if I had a backup of the
data...

Jan

  reply	other threads:[~2006-02-08 22:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 20:39 VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day Jan Dittmer
2006-02-08  0:23 ` Andrew Morton
2006-02-08  7:48   ` Jan Dittmer
2006-02-08 18:06     ` Balbir Singh
2006-02-08 22:42       ` Jan Dittmer [this message]
2006-02-09  4:02         ` Balbir Singh
  -- strict thread matches above, loose matches on Subject: below --
2006-12-28  9:27 Jesper Juhl
2006-12-28  9:43 ` Jan Engelhardt
2006-12-28 10:32 ` Ian Kent
2001-07-29 19:13 David Ford

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=43EA73C9.7010101@l4x.org \
    --to=jdi@l4x.org \
    --cc=akpm@osdl.org \
    --cc=bsingharora@gmail.com \
    --cc=dev@sw.ru \
    --cc=jblunck@suse.de \
    --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