search for: prabhakaran

Hi, I'm using linux 2.4.25 and I'm trying to change the wakeup interval of kupdate daemon. Is there a way to change that ? I once used 'update' tool for that. But that is not there in 2.4.25. Has it been removed ? I appreciate any help regarding this. thanks, Vijayan

Hi, Is it possible to use a separate journal device (one on a separate drive or a partition) shared among more than 1 Ext3 file systems ? I appreciate any inputs. thanks, Vijayan

Hi, Is there any way that one can change the location of the journal file when the file system is created ? For eg., instead of using inode# 7 and the blocks at the beginning of the file system, I'd like to use an inode at a different cylinder group and some other set of blocks. Even if I'm allowed only to use one of the reserved inodes, is it possible to put the journal file somewhere in

Hi, I have a question on fsync() and ext3's journaling modes. Assume that I call fsync(fd) on a file. If that file is in 'data=journal' mode, would the fsync() return once the data gets safely into the journal ? On the other hand, if that file is in 'data=writeback' mode, would the fsync() return only when the data gets safely into its actual location ? Any help is

Hi, I have a doubt on how the transaction semantics work in ext3. When I copy a file, does the entire copy is treated as one transaction so that finally I have either the full file or no file. Or will it be split into multiple transactions which can result in copying partial files. thanks, Vijayan

Hi, I have a doubt in the ordering of writes in ext3. Any help is appreciated. Ext3 enforces certain ordering in writes to ensure data integrity. For example, the journal writes are issued first and only after their successful completion the actual writes are issued. Sometimes we need to maintain ordering across transactions also. This is needed because if the actual writes of one transaction

...* Program Committee: o Angelos Bilas, FORTH and University of Crete o Randal Burns, Johns Hopkins University o Dan Feng, Huazhong University of Science and Technology o Dirk Grunwald, University of Colorado, Boulder o Ajay Gulati, VMware o Ron Oldfield, Sandia National Laboratory o Vijayan Prabhakaran, Microsoft Research o Himabindu Pucha, IBM Research - Almaden o A. L. Narasimha Reddy, Texas A&M University o Alma Riska, College of William and Mary o Philip Roth, Oak Ridge National Laboratory o Jiri Schindler, NetApp o Rajeev Thakur, Argonne National Laboratory o Bhuvan Urgaonkar, Pen...

...* Program Committee: o Angelos Bilas, FORTH and University of Crete o Randal Burns, Johns Hopkins University o Dan Feng, Huazhong University of Science and Technology o Dirk Grunwald, University of Colorado, Boulder o Ajay Gulati, VMware o Ron Oldfield, Sandia National Laboratory o Vijayan Prabhakaran, Microsoft Research o Himabindu Pucha, IBM Research - Almaden o A. L. Narasimha Reddy, Texas A&M University o Alma Riska, College of William and Mary o Philip Roth, Oak Ridge National Laboratory o Jiri Schindler, NetApp o Rajeev Thakur, Argonne National Laboratory o Bhuvan Urgaonkar, Pen...

Hi, Well, this might not be the right place to pose this question. But, I'm sure that there are people who can answer this. My question is regarding how disk errors are reported to ext3. From my basic understanding of the block driver routines, it seems that all the different types of disk errors (like sector failures, scsi bus timeout, etc) are converted into one single error code (EIO) and

Hi, I ran a set of benchmarks over different combinations of ext3 journaling on mirrored disks. I got some non-intuitive results. Could someone help me reason this ? Benchmarks ---------- I ran concurrently 4 processes, each process having a working set of 10MB. a) Process 0 creates 160 files each of size 64KB. b) Process 1 reads 160 files each of size 64KB. c) Process 2 creates 2560 dirs.