Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #37220
| Newsgroups | comp.os.linux.misc |
|---|---|
| From | "25B.E866" <25B.E866@noaaba.net> |
| Subject | Int64 File Seeking ??? |
| Organization | protonic seahorse |
| Date | 2023-02-22 01:52 -0500 |
| Message-ID | <Uh2cnczb7I4tJmj-nZ2dnZfqnPWdnZ2d@earthlink.com> (permalink) |
I arrived at a need to search hard drives - like up to 16 terabyte hard drives - AND kinda show what's going on. THE problem is that if you need to look at a SPECIFIC spot on the disk the usual "seek()" functions crap out - limited to longint (about 2.4 gig). Free Pascal CLAIMS its fseek() will take an int64 ... but in practice I see the exact same bits of the disk come up again, which means it's rolling over. Just started experimenting with Python - I'll know in a day or two. The GCC lib - sometimes requiring special flags - claims it'll do 64-bit seeks - but I haven't confirmed that yet either. Consider 'dd' ... you can copy all, or parts of, huge disks. Tell it to start at the 3tb mark and it'll do it. I'm not sure if that uses any of the standard 'C' libraries or is something totally custom under the hood. It IS kinda slow alas - try duplicating, or even zeroing, a 12tb disk sometime ... better start on friday afternoon ...... A lot of languages/compilers were refined when the old 2 gb files were kind of the max. You CAN view a big disk AS a file if need be. The world moved on, but it seems THEY didn't. Any insights ???
Back to comp.os.linux.misc | Previous | Next — Next in thread | Find similar
Int64 File Seeking ??? "25B.E866" <25B.E866@noaaba.net> - 2023-02-22 01:52 -0500
Re: Int64 File Seeking ??? Richard Kettlewell <invalid@invalid.invalid> - 2023-02-22 08:55 +0000
Re: Int64 File Seeking ??? The Natural Philosopher <tnp@invalid.invalid> - 2023-02-22 13:38 +0000
Re: Int64 File Seeking ??? Richard Kettlewell <invalid@invalid.invalid> - 2023-02-22 14:11 +0000
Re: Int64 File Seeking ??? "25B.E866" <25B.E866@noaaba.net> - 2023-02-22 20:38 -0500
Re: Int64 File Seeking ??? "25B.E866" <25B.E866@noaaba.net> - 2023-02-22 23:53 -0500
Re: Int64 File Seeking ??? Robert Riches <spamtrap42@jacob21819.net> - 2023-02-23 05:11 +0000
Re: Int64 File Seeking ??? Bobbie Sellers <bliss@mouse-potato.com> - 2023-02-22 21:29 -0800
Re: Int64 File Seeking ??? "25B.E866" <25B.E866@noaaba.net> - 2023-02-23 00:49 -0500
Re: Int64 File Seeking ??? The Natural Philosopher <tnp@invalid.invalid> - 2023-02-24 13:13 +0000
Re: Int64 File Seeking ??? Richard Kettlewell <invalid@invalid.invalid> - 2023-02-24 14:58 +0000
Re: Int64 File Seeking ??? Pancho <Pancho.Jones@proton.me> - 2023-02-24 15:13 +0000
Re: Int64 File Seeking ??? "25A.I866" <25A.I866@noacba.net> - 2023-02-26 00:05 -0500
Re: Int64 File Seeking ??? "25A.I866" <25A.I866@noacba.net> - 2023-02-25 23:58 -0500
Re: Int64 File Seeking ??? "25B.E866" <25B.E866@noaaba.net> - 2023-02-22 10:14 -0500
Re: Int64 File Seeking ??? Bobbie Sellers <bliss@mouse-potato.com> - 2023-02-22 08:52 -0800
Re: Int64 File Seeking ??? The Natural Philosopher <tnp@invalid.invalid> - 2023-02-22 16:55 +0000
Re: Int64 File Seeking ??? Bobbie Sellers <bliss@mouse-potato.com> - 2023-02-22 12:36 -0800
Re: Int64 File Seeking ??? "Carlos E.R." <robin_listas@es.invalid> - 2023-02-24 20:50 +0100
csiph-web