search for: datablock

Hi all, i wanted to ask you all about the exact overwrite mechanism used in ext3; is the information in the datablocks overwritten or written to a new location and the information in the referring inode is changed? Is it depending on the application used (and the functions it calls) or independent from that? Please don't hesitate to go into further details and thanks for your help! cheers, flo This messa...

...ormation from the existing ext2/ext3 filesystem. Why there are ext2_inode datastructure defined in these programs ? Why couldn't these programs read existing datastructures of inode ? 3. Are these user level or kernel level programs ? 4. I want to have my own policies of allocatiing datablocks in some cylinder group instead of using ext2 default policy ? What should I do for that ? I know, these must be silly questions, but I will learn from your response. Mir. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/e...

Is there such a filesystem available? It seems like it wouldn't be too hard to implement... Basically do things on a block by block basis. Store md5 of a block in the table, and when writing a new block, check if the md5 already exists and then point the new block to the old block. Since md5 is not guaranteed unique, might need to do a diff between the 2 blocks and if the blocks are indeed

...if (parse_uint32 (&ret->logblocksize, buf) == -1) + goto error; + else goto error; + } else if (p = strstr (lines[i], "blocks=")) { + buf = split_strdup (p + 7); + if (buf == NULL) goto error; + if (i == 2) + if (parse_uint64 (&ret->datablocks, buf) == -1) + goto error; + else if (i == 5) + if (parse_uint32 (&ret->logblocks, buf) == -1) + goto error; + else if (i == 7) + if (parse_uint64 (&ret->rtblocks, buf) == -1) + goto error; + else goto error; + } else if (p =...

...h to rsync, whereas this time I was doing individual files. I'm guessing that caused a different default behavior. After I started using --no-whole-file and --inplace, the situation improved. For files that had few differences, it was quite fast. However, for files that had lots of modified datablocks, it was still taking much longer than an rcp would. An rcp of a 4gb datafile took about seven minutes whereas rsync with about 10% modified data took about half an hour as shown: -- > Syncing Datafile: /c03/oradata/can/ard04.dbf @ Fri Aug 26 11:46:08 EDT 2005 Number of files: 1 Number of fi...

...s at about line 1831 of fs/jbd/transaction.c and has the comment: /* If it is committing, we simply cannot touch it. We * can remove it's next_transaction pointer from the * running transaction if that is set, but nothing * else. */ This code really must arrange that a data=journal datablock never gets marked as dirty again (note that it isn't actualy dirty at this point, it is JBDDirty instead, to stop if from being written to disc prematurey). One option might be to simply clear the JBDDirty flag at this point. However this causes a number of assertions later on to fail, so it...

I''ve noticed that using several TimedObservers (prototype.js) on a page to watch for changes to text fields (haven''t tried forms) can have a non-negligible effect on the CPU cycles used by the browser process. Nothing dramatic, to be sure, but unnecessary. Autocompleter.Base (controls.js) follows a smarter strategy to watch for changes. Currently this functionality is tied

...on used to initalise the Vorbis stream. This setup information MUST be completely intact and a client can not decode a stream with an incomplete or corrupted codebook set. A 16 bit codebook length field and a 16 bit 1's complement checksum of the codebook precedes the codebook datablock. The length field allows for codebooks to be upto 64k in size. The checksum is used to detect a corrupted codebook. If a checksum failure is detected then a new config header file SHOULD be obtained from SDP. If no SDP value is set and no other method for obtaining the config hea...

...ot; from node 2 in directory /u01/oracle/prod/proddata it locks up in a "D" state. From node 1 all is well. if i were to shutdown instance 1 of RAC and unmount the /u01 partition on u01 all processes on node 2 would immediately resume. (this has happened before.) Seems like a inode or datablock locking issue and/or race condition... it's locked up right now; i don't really know what to look for but here's some diagnostics info - can somebody make any sense of this? i can leave it locked up for a day or two so if anyone would like to see output from a debugocfs command before...

Bellow, follows a proposal for a new opensolaris project. Of course, this is open to change since I just wrote down some ideas I had months ago, while researching the topic as a graduate student in Computer Science, and since I''m not an opensolaris/ZFS expert at all. I would really appreciate any suggestion or comments. PROJECT PROPOSAL: ZFS Compression Algorithms. The main purpose of

...| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | codebook checksum | codebook ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ A 16 bit 1's complement checksum of the codebook precedes the codebook datablock. This checksum is used to detect a corrupted codebook. If a checksum failure is detected an empty RR RTCP message, of APP type with the 4 octet name field set to VORR, is sent from the client. Transmission of the codebook back to the client SHOULD be handled as an unicast delivery...

...| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | codebook checksum | codebook ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ A 16 bit 1's complement checksum of the codebook precedes the codebook datablock. This checksum is used to detect a corrupted codebook. If a checksum failure is detected an empty RR RTCP message, of APP type with the 4 octet name field set to VORR, is sent from the client. <p><p><p><p> Expires July 7, 2003...

...| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | codebook checksum | codebook ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ A 16 bit 1's complement checksum of the codebook precedes the codebook datablock. This checksum is used to detect a corrupted codebook. If a checksum failure is detected an empty RR RTCP message, of APP type with the 4 octet name field set to VORR, is sent from the client. Transmission of the codebook back to the client SHOULD be handled as an unicast delivery...

...| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | codebook checksum | codebook ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ A 16 bit 1's complement checksum of the codebook precedes the codebook datablock. This checksum is used to detect a corrupted codebook. If a checksum failure is detected an empty RR RTCP message, of APP type with the 4 octet name field set to VORR, is sent from the client. Transmission of the codebook back to the client SHOULD be handled as an unicast delivery...

...| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | codebook checksum | codebook ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ A 16 bit 1's complement checksum of the codebook precedes the codebook datablock. This checksum is used to detect a corrupted codebook. If a checksum failure is detected an empty RR RTCP message, of APP type with the 4 octet name field set to VORR, is sent from the client. Transmission of the codebook back to the client SHOULD be handled as an unicast delivery...

Hello, I have my work on the nv vpe video decoder in a functional state. In case you didn't know this decoder accelerates mpeg2 video at the idct/mc level. I have verified that it works on nv40 hardware. I believe it works on nv30 hardware (and maybe some earlier hardware), but I cannot verify since I have none. I will reply with patches against the kernel, drm, ddx and mesa for

...ain the codebook configuration data. This setup information MUST be completely intact and a client can not decode a stream with an incomplete or corrupted codebook set. A 16 bit codebook length field and a 16 bit 1's complement checksum of the codebook precedes the codebook datablock. The length field allows for codebooks to be upto 64k in size. The checksum is used to detect a corrupted codebook. Kerr Expires December 10, 2003 [Page 10] Internet Draft draft-kerr-avt-vorbis-rtp-02.txt June 10, 2003 <p>If a checksum f...

.../* fsblocks in an AG */ + uint32_t agcount; /* number of allocation groups */ + uint32_t logblocks; /* fsblocks in the log */ + uint32_t sectsize; /* (data) sector size, bytes */ + uint32_t inodesize; /* inode size in bytes */ + uint32_t imaxpct; /* max allowed inode space(%) */ + uint64_t datablocks; /* fsblocks in data subvolume */ + uint64_t rtblocks; /* fsblocks in realtime subvol */ + uint64_t rtextents; /* rt extents in realtime subvol*/ + uint64_t logstart; /* starting fsblock of the log */ + unsigned char uuid[16]; /* unique id of the filesystem */ + uint32_t sunit; /* stripe unit...

https://bugzilla.samba.org/show_bug.cgi?id=13317 Bug ID: 13317 Summary: rsync returns success when target filesystem is full Product: rsync Version: 3.1.2 Hardware: x64 OS: FreeBSD Status: NEW Severity: major Priority: P5 Component: core Assignee: wayned at samba.org

Hi, when mounting an intentionally corrupted btrfs filesystem i get the following warning and bug message. The image can be found here www.cccmz.de/~snakebyte/btrfs.2.img.bck.bz2 [ 297.406152] device fsid e14cf01de423381a-4bd40b603870018a <6>devid 2147483649 transid 9 /dev/loop0 [ 297.411937] ------------[ cut here ]------------ [ 297.412207] WARNING: at fs/btrfs/disk-io.c:805