| To: | Linux XFS <linux-xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: file corruption during emacs build on XFS logical volume |
| From: | Sean Neakums <sneakums@xxxxxxxx> |
| Date: | Fri, 04 Jan 2002 18:04:52 +0000 |
| In-reply-to: | <1010164935.1945.8.camel@UberGeek> (Austin Gonyou's message of "04 Jan 2002 11:22:15 -0600") |
| Mail-followup-to: | Linux XFS <linux-xfs@xxxxxxxxxxx> |
| References: | <1010141444.1992.3.camel@pyewacket> <1010164935.1945.8.camel@UberGeek> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1 (i386-debian-linux-gnu) |
begin Austin Gonyou quotation: > No, It does not guarantee. Also, if you're not on the same Inode the > file time is different, etc, it's possible to have different md5sums. A > basic size and file comparison is probably best for what you want to do. The md5sum of a file is based on its contents only. The inode has nothing to do with it. > Something you can do to test what I'm talking about is copy each of your > dumps to another name, binfilexyz.1 or something, then compare it's > md5sum against the original. Those should be the only time they match. I'm not sure exaclty what you mean by this. The name of the file is irrelevant in the computation of the md5sum. -- ///////////////// | | The spark of a pin <sneakums@xxxxxxxx> | (require 'gnu) | dropping, falling feather-like. \\\\\\\\\\\\\\\\\ | | There is too much noise. |
| Previous by Date: | Re: file corruption during emacs build on XFS logical volume, Austin Gonyou |
|---|---|
| Next by Date: | SAMBA 2.2.2 AND XFS QUOTA SUPPORT, Fabrizio Celli |
| Previous by Thread: | Re: file corruption during emacs build on XFS logical volume, Austin Gonyou |
| Next by Thread: | Re: file corruption during emacs build on XFS logical volume, Sean Neakums |
| Indexes: | [Date] [Thread] [Top] [All Lists] |