FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > EXT3 Users

 
 
LinkBack Thread Tools
 
Old 07-22-2008, 01:02 PM
"Eli Dorfman"
 
Default ext3 filesystem becomes read-only

Hello all,

I have the following setup:
iSCSI initiator on RHEL5.
ISCSI target on RHEL5.1

I created an ext3 FS on the device
# mkfs.ext3 /dev/sdc

mounted the device
# mount /dev/sdc /mnt/sdc

Trying to create a file on the mounted FS
# dd if=/dev/zero of=/mnt/sdc/tempfile bs=1k count=10M

I got the following error on the initiator:

dd: writing `/mnt/sdc/tempfile': Read-only file system
1489+0 records in
1488+0 records out

This problem happens only with ext3 but not with ext2 and when created
file is larger than 4GB.

Please advise.

Following is the output of /var/log/messages:

Jul 22 15:16:53 nsg1 kernel: EXT3 FS on sdd, internal journal
Jul 22 15:16:53 nsg1 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 22 15:22:35 nsg1 kernel: EXT3-fs error (device sdd):
ext3_new_block: Allocating block in system zone - blocks from 2719744,
length 1
Jul 22 15:22:35 nsg1 kernel: Aborting journal on device sdd.
Jul 22 15:22:35 nsg1 kernel: ext3_abort called.
Jul 22 15:22:35 nsg1 kernel: EXT3-fs error (device sdd):
ext3_journal_start_sb: Detected aborted journal
Jul 22 15:22:35 nsg1 kernel: Remounting filesystem read-only
Jul 22 15:22:35 nsg1 kernel: EXT3-fs error (device sdd):
ext3_free_blocks: Freeing blocks in system zones - Block = 2719744,
count = 1
Jul 22 15:22:35 nsg1 kernel: EXT3-fs error (device sdd) in
ext3_free_blocks_sb: Journal has aborted
Jul 22 15:22:37 nsg1 kernel: __journal_remove_journal_head: freeing
b_committed_data
Jul 22 15:22:37 nsg1 last message repeated 9 times
Jul 22 15:22:37 nsg1 kernel: __journal_remove_journal_head: freeing
b_frozen_data
Jul 22 15:22:37 nsg1 kernel: __journal_remove_journal_head: freeing
b_committed_data
Jul 22 15:22:37 nsg1 kernel: __journal_remove_journal_head: freeing
b_frozen_data


Thanks,
Eli

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 
Old 07-22-2008, 03:07 PM
Eric Sandeen
 
Default ext3 filesystem becomes read-only

Eli Dorfman wrote:
> Hello all,
>
> I have the following setup:
> iSCSI initiator on RHEL5.
> ISCSI target on RHEL5.1
>
> I created an ext3 FS on the device
> # mkfs.ext3 /dev/sdc
>
> mounted the device
> # mount /dev/sdc /mnt/sdc
>
> Trying to create a file on the mounted FS
> # dd if=/dev/zero of=/mnt/sdc/tempfile bs=1k count=10M
>
> I got the following error on the initiator:
>
> dd: writing `/mnt/sdc/tempfile': Read-only file system
> 1489+0 records in
> 1488+0 records out

> This problem happens only with ext3 but not with ext2 and when created
> file is larger than 4GB.
>
> Please advise.


Is it unique to iscsi? i.e. what if you do the same thing directly on
the target?

And, being iscsi, is anything else accessing the same block device on
the target?

-Eric

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 
Old 07-22-2008, 04:00 PM
"Eli Dorfman"
 
Default ext3 filesystem becomes read-only

>> Hello all,
>>
>> I have the following setup:
>> iSCSI initiator on RHEL5.
>> ISCSI target on RHEL5.1
>>
>> I created an ext3 FS on the device
>> # mkfs.ext3 /dev/sdc
>>
>> mounted the device
>> # mount /dev/sdc /mnt/sdc
>>
>> Trying to create a file on the mounted FS
>> # dd if=/dev/zero of=/mnt/sdc/tempfile bs=1k count=10M
>>
>> I got the following error on the initiator:
>>
>> dd: writing `/mnt/sdc/tempfile': Read-only file system
>> 1489+0 records in
>> 1488+0 records out
>
>> This problem happens only with ext3 but not with ext2 and when created
>> file is larger than 4GB.
>>
>> Please advise.
>
>
> Is it unique to iscsi? i.e. what if you do the same thing directly on
> the target?

it works directly.
the problem happens only with iscsi (iser transport) with ext3 filesystem.
iscsi with ext2 works.

>
> And, being iscsi, is anything else accessing the same block device on
> the target?

No.

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
 

Thread Tools




All times are GMT. The time now is 02:20 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org