From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: gene.heskett@verizon.net
Cc: linux-kernel@vger.kernel.org, Nigel Kukard <nkukard@lbsd.net>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Subject: Re: 2.6.9bk6 msdos fs OOPS
Date: Fri, 29 Oct 2004 04:50:56 +0900 [thread overview]
Message-ID: <87zn261v1b.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <200410281432.01013.gene.heskett@verizon.net> (Gene Heskett's message of "Thu, 28 Oct 2004 14:32:00 -0400")
Gene Heskett <gene.heskett@verizon.net> writes:
> Now, how about its going read-only on me if I move (and delete) say 33
> pix at the head of the its directory listing? Is this an M$ related
> fs bug in the camera?
>
> Thats required some contortions like camera battery removal, reboot
> this machine, etc to alleviate and restore normal operations in the
> past.
Umm... When filesystem became to read-only, is there the messages from
kernel (output of dmesg)?
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2004-10-28 19:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 7:00 2.6.9bk6 msdos fs OOPS Nigel Kukard
2004-10-28 7:55 ` Denis Vlasenko
2004-10-28 8:11 ` Nigel Kukard
2004-10-28 9:23 ` OGAWA Hirofumi
2004-10-28 10:50 ` Nigel Kukard
2004-10-28 13:18 ` OGAWA Hirofumi
2004-10-28 11:14 ` Gene Heskett
2004-10-28 11:59 ` Gene Heskett
2004-10-28 12:12 ` Gene Heskett
2004-10-28 13:21 ` OGAWA Hirofumi
2004-10-28 15:24 ` Nigel Kukard
2004-10-28 15:58 ` OGAWA Hirofumi
2004-10-28 18:32 ` Gene Heskett
2004-10-28 18:32 ` Gene Heskett
2004-10-28 19:50 ` OGAWA Hirofumi [this message]
2004-10-28 23:05 ` Gene Heskett
2004-10-29 0:01 ` OGAWA Hirofumi
2004-10-29 4:50 ` Gene Heskett
2004-10-29 5:31 ` Gene Heskett
2004-10-28 8:21 ` Al Viro
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=87zn261v1b.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nkukard@lbsd.net \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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.