Re: BUG IN REISERFS
Masthan, Dudekula (STSD) wrote: > > >Hi Folks, > >Mkreiserfs command is failing by showing " There are no enoguh blocks on >this device" , What is the minimum size of a disk to create reiserfs >file system > >Regards, >Masthan > > > > > Please modify the error message so that it answers his question before users think to ask it.:) Hans
Re: BUG IN REISERFS
hello On Fri, 2006-06-30 at 17:51 +0530, Masthan, Dudekula (STSD) wrote: > > Hi Folks, > > Mkreiserfs command is failing by showing " There are no enoguh blocks on > this device" , What is the minimum size of a disk to create reiserfs > file system > Please let us see whole mkreiserfs output and the command line itself. In case of standard journal minimal reiserfs size is 8212 blocks. > Regards, > Masthan > >
Re: BUG IN REISERFS
Please choose your subject carefully. Claiming that you found a bug in reiserfs while you only met a boundary condition isn't very polite. On Fri, Jun 30, 2006 at 05:51:14PM +0530, Masthan, Dudekula (STSD) wrote: > Mkreiserfs command is failing by showing " There are no enoguh blocks on > this device" , What is the minimum size of a disk to create reiserfs > file system That mainly depends on the journal size. The default journal size is 32 MB which means that an actual useful disk size is about 100 MB. See mkreiserfs(8), -s option. Erik -- +-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 -- | Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
BUG IN REISERFS
Hi Folks, Mkreiserfs command is failing by showing " There are no enoguh blocks on this device" , What is the minimum size of a disk to create reiserfs file system Regards, Masthan
Re: BUG IN REISERFS SLES 10 :
Hello
On Fri, 2006-06-30 at 11:08 +0530, Masthan, Dudekula (STSD) wrote:
> Hi Folks,
>
> I am using SLES 10 latest beta bits. Generally I will use sg_reset
> command to reset my scsi device/bus. In sles 10 the machine is not
> coming up ( or in otherwords the machine is hanging) after issuing the
> sg_reset command.
> I tried the following command
>
> # sg_reset -b /dev/sg3
>
> and also i tried with scsi ioctls, still I am facing the same problem
> I tried with the following standalone program
>
> #include
>:
>:
> int main(int argc, char * argv[]) {
>int fd;
>int rc;
>int arg=2;
>if ((fd=open("/dev/sg3", O_RDWR)) < 0) {
> printf( "device open fails");
> return -1;
>}
>if ((rc=ioctl(fd,SG_SCSI_RESET,&arg)) < 0 ){
> printf( " ioctl failed ");
> close (fd);
> return -1;
>}
>
> printf ( " reset success ");
> close (fd);
> return 0;
> }
>
>
> After running above program also I am facing same problem.
>
>
> Is it bug in SLES 10 or is it bug in qlogic driver ?
>
To check whether it is filesystem problem you may want to try something
like:
mknod /ext2-mount/sg3 c 21 3
and then try your program patched with the below:
- if ((fd=open("/dev/sg3", O_RDWR)) < 0) {
+ if ((fd=open("/ext2-mount/sg3", O_RDWR)) < 0) {
> Thanks in advance
>
BUG IN REISERFS SLES 10 :
Hi Folks,
I am using SLES 10 latest beta bits. Generally I will use sg_reset
command to reset my scsi device/bus. In sles 10 the machine is not
coming up ( or in otherwords the machine is hanging) after issuing the
sg_reset command.
I tried the following command
# sg_reset -b /dev/sg3
and also i tried with scsi ioctls, still I am facing the same problem
I tried with the following standalone program
#include
:
:
int main(int argc, char * argv[]) {
int fd;
int rc;
int arg=2;
if ((fd=open("/dev/sg3", O_RDWR)) < 0) {
printf( "device open fails");
return -1;
}
if ((rc=ioctl(fd,SG_SCSI_RESET,&arg)) < 0 ){
printf( " ioctl failed ");
close (fd);
return -1;
}
printf ( " reset success ");
close (fd);
return 0;
}
After running above program also I am facing same problem.
Is it bug in SLES 10 or is it bug in qlogic driver ?
Thanks in advance
Re: BUG in Reiserfs Journal Thread
I'm using reiserfs 3.6 with the data journaling patch from ftp://ftp.suse.com/pub/people/mason/patches/data-logging/2.4.25/. On Wed, 15 Sep 2004 16:07:16 -0400, Chris Mason <[EMAIL PROTECTED]> wrote: > On Wed, 2004-09-15 at 16:02, Vijayan Prabhakaran wrote: > > Dear Chris Mason, > > > > I found a bug in Reiserfs journal thread. This bug is in function > > reiserfs_journal_commit_thread(). > > Hi, > > Which version of the code are you reading? > > -chris > >
Re: BUG in Reiserfs Journal Thread
On Wed, 2004-09-15 at 16:02, Vijayan Prabhakaran wrote: > Dear Chris Mason, > > I found a bug in Reiserfs journal thread. This bug is in function > reiserfs_journal_commit_thread(). Hi, Which version of the code are you reading? -chris
BUG in Reiserfs Journal Thread
Dear Chris Mason,
I found a bug in Reiserfs journal thread. This bug is in function
reiserfs_journal_commit_thread().
I'm trying to measure the impact of journal thread on data flushes. I
changed the commit interval from the default of 5 seconds (this value
is hard coded in the function) to other different values. I found that
irrespective of changing the journal thread's timer value, the dirty
data was not getting flushed after the time out at the commit thread.
The reason for this is due to a bug in the code. The code looks like
while(1) {
/*blah blah blah*/
if (CURRENT_TIME - last_run > 5) {
reiserfs_flush_old_commits(s);
}
/*blah blah blah*/
interruptible_sleep_on_timeout(&reiserfs_commit_thread_wait, 5 * HZ) ;
/*thread wakes up*/
}
If you see the code, the thread sleeps for 5 seconds. But after waking
up, it again checks the condition:
if (CURRENT_TIME - last_run > 5) {
reiserfs_flush_old_commits(s);
}
Actually, the condition should be ">=" instead of ">". Since the
thread wakes up immediately after the timer expires, the condition
will never satisfy if it is ">".
Chris, can you please verify this and add the fix ?
I appreciate your help.
Vijayan
