What is filesystem panic?

Per Anton Rønning pa-ronn at online.no
Wed Oct 29 18:53:00 UTC 2008


Mikkel L. Ellertson wrote:
> Per Anton Rønning wrote:
>   
>> But now the pen seems to be really stuck, just look at this:
>>
>> [root at localhost disk]# /sbin/fdisk /dev/sdc
>> Unable to open /dev/sdc
>>
>> And also:
>> [root at localhost disk]# /sbin/fdisk /dev/sdc1
>> Unable to open /dev/sdc1
>>
>> This is not a disaster, it just means that I have to consider this flash
>> pen obsolete and buy a new one.
>> I have been using it for backup of some hard disk directories,  so it is
>> no big deal if I lose whats on it, since my harrdisk is intact.
>>
>> Perhaps I should buy a  removable HD instead.
>>
>> BRGDS
>> PAR
>>
>>     
> Plug the drive in, and then run "tail /var/log/messages" to see what
> messages are generated. I would not be surprised to if the problem
> was that the drive was assigned a different letter. Also, you do not
> want to use fdisk on anything but the base drive. Using it on
> /dev/sdc1 will produce all kinds of interesting errors on a good drive.
>
> Mikkel
>   
It goes like this:
[root at localhost trade]# tail /var/log/messages
Oct 29 19:47:26 localhost kernel: sd 9:0:0:0: [sdf] Write Protect is off
Oct 29 19:47:26 localhost kernel: sd 9:0:0:0: [sdf] Assuming drive 
cache: write through
Oct 29 19:47:26 localhost kernel: sd 9:0:0:0: [sdf] 7987198 512-byte 
hardware sectors (4089 MB)
Oct 29 19:47:26 localhost kernel: sd 9:0:0:0: [sdf] Write Protect is off
Oct 29 19:47:26 localhost kernel: sd 9:0:0:0: [sdf] Assuming drive 
cache: write through
Oct 29 19:47:26 localhost kernel: sdf: sdf1
Oct 29 19:47:26 localhost kernel: sd 9:0:0:0: [sdf] Attached SCSI 
removable disk
Oct 29 19:47:26 localhost kernel: sd 9:0:0:0: Attached scsi generic sg6 
type 0
Oct 29 19:47:27 localhost hald: mounted /dev/sdf1 on behalf of uid 500
Oct 29 19:47:27 localhost gnome-keyring-daemon[2721]: adding removable 
location: volume_uuid_7A22_FF86 at /media

I cannot see anything here pointing to an error situation (?) It does 
not even report that it set to write-only.
But it is still write-only.

I was only trying fdisk to see if it would disclose anything, but it did 
not get that far.

Brgds
PAR




More information about the fedora-list mailing list