search for: pread64

I have accidently damaged the first block(s) of a btrfs partition and can''t mount it anymore. I can see that my data is still intact by running a command like: cat /dev/sda5 | hexdump -C | more Do any (experimental) tools exist which would allow me to recover the files? Thank you -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a

..., only the absolute execution times are a little better. I have got samba logfiles at loglevel 10 (about 30MB on the Solaris system, about 1900MB on the Linux servers), also Samba process trace files (with strace under Linux and truss under Solaris) I found that under Solaris, Samba executes 4866 pread64(2) system calls for the whole run, while under Linux more than 325000(!) pread64(2) system calls are executed (for the same client application!) Looking at the Samba Logfiles, the first 190000 lines or so are almost identical between Solaris and Linux systems. Here the application opens its contro...

...\n 6 4".., 5120) = 1188 read(8, 0xFFBFE4FC, 3932) = 0 open64("/var/qmail/maildirs/09/44/XXXXXX/Maildir/cur/1186631443.M495843P21207V000000940000BF68I000000000030AFC0_0.recess4,S=803364:2,S", O_RDONLY) = 10 fstat64(10, 0xFFBFF2A0) = 0 pread64(10, " A g I C A 8 d G Q g Y 2".., 4096, 58982) = 4096 pread64(10, " R p b m c 9 I j A i P g".., 4096, 63078) = 4096 pread64(10, " O V 8 w M D F f M D M y".., 4096, 67174) = 4096 pread64(10, " Z W M v Y X M v M j A w".., 4096, 71270) = 4096 pread64(10, "...

..., only the absolute execution times are a little better. I have got samba logfiles at loglevel 10 (about 30MB on the Solaris system, about 1900MB on the Linux servers), also Samba process trace files (with strace under Linux and truss under Solaris) I found that under Solaris, Samba executes 4866 pread64(2) system calls for the whole run, while under Linux more than 325000(!) pread64(2) system calls are executed (for the same client application!) Looking at the Samba Logfiles, the first 190000 lines or so are almost identical between Solaris and Linux systems. Here the application opens its contro...

...= 0 fcntl(12, F_SETLKW64, 0xFFBFED38) = 0 alarm(0) = 5 stat64("/home/hrz/g033/Mail/test-ein", 0xFFBFEF80) = 0 stat64("/home/hrz/g033/Mail/.imap/test-ein/dovecot.index.log", 0xFFBFEA28) = 0 pread64(11, 0x00083090, 8192, 4440) = 0 stat64("/home/hrz/g033/Mail/.imap/test-ein/dovecot.index.log", 0xFFBFEEC0) = 0 pread64(11, 0x00083090, 8192, 4440) = 0 fstat64(12, 0xFFBFF1F0) = 0 brk(0x00092498) = 0 brk(0x0009...

...\3%\0\0\4\377\376\377\357?\4", 1024) = 19 [pid 27922] read(16, "", 1005) = 0 [pid 27922] close(16) = 0 [pid 27922] open("/var/data/vmail/private/pdf/xapian.db/record.baseB", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 27922] pread64(10, "\0\0\0\4\1\0362\0362\0Q\37\371\37\356\37\343\37\330\37\315\37\302\37\267\37\254\37\241\37\226\37"..., 8192, 147456) = 8192 [pid 27922] open("/var/data/vmail/private/pdf/xapian.db/spelling.DB", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 27922] open(&q...

I found something interesting via strace. lda is writing a timestamp with utime before doign the fsync, but I'm really not a C guy, so I have no idea why that's going on via procmail and not via commandline. I assume it's related to the choice of pread64 vs read. when called from commandline (working): read(0, "July 14-20, 2013\n10 courses. Bon"..., 4096) = 4096 read(0, "s bigger\nthan most realistic cyb"..., 4096) = 4096 read(0, "olina company in\nnumerous small,"..., 4096) = 4096 read(0, "on't have any way...

...s output: 12951: stat64("/home/happy/Mail/banner-ss", 0xFFBFF200) = 0 12951: fstat64(12, 0xFFBFF388) = 0 12951: stat64("/home/happy/Mail/.imap/banner-ss/dovecot.index", 0xFFBFF2F0) = 0 12951: fstat64(18, 0xFFBFF388) = 0 12951: pread64(18, "\n F r o m b e v e r l".., 4096, 1592560) = 4096 12951: pread64(18, " S u n G a r d * S C".., 4094, 1596656) = 4094 12951: pread64(18, " M i c r o s o f t S a".., 4094, 1600750) = 4094 12951: pread64(18, " r g a r e t . d i l l a".., 4094, 160...

Hi all, Does anyone happen to know if there are *any* 32-bit architectures (on which Linux runs) for which the ABI for a "long long" is different from passing two "longs" in the appropriate order, i.e. (hi,lo) for bigendian or (lo,hi) for littleendian? I'd like to switch klibc to use the 64-bit file ABI thoughout, but it's a considerable porting effort, and

...510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Sender: torrents at rutracker.org Reply-to: torrents at rutracker.org From: torrents at rutracker.org Message-ID: <6162ed30245a86b8cb26e4a0bf4de562 at rutracker.org> [...] --- 3.strace show, that dovecot many-many time do: --- pread64(6, "-Sender: torrents at rutracker.org\n"..., 4038, 814845) = 4038 pread64(6, "s at rutracker.org\nMessage-ID: <461"..., 4083, 818883) = 4083 pread64(6, "arset=windows-1251\nContent-trans"..., 4068, 822966) = 4068 pread64(6, "ail-Priority: Normal\nX-Mailer: M&q...

...n/Maildir/dovecot-uidlist.lock", 0x080476C0) = 0 unlink("/var/mail/apps/domain/admin/Maildir/dovecot-uidlist.lock") = 0 open64("/var/mail/apps/domain/admin/Maildir/cur/1199514786.M867961P7368.vds5,W=1325:2,", O_RDONLY) = 9 fstat64(9, 0x080477A0) = 0 pread64(9, " R e t u r n - P a t h :".., 4096, 0) = 1298 pread64(9, " R e t u r n - P a t h :".., 4096, 0) = 1298 close(9) = 0 write(2, "01 P f i l e i n d e x".., 82) = 82 getcontext(0x08047510) open("/proc/self/as", O_R...

...-dev/cur", {st_mode=S_IFDIR|0700, st_size=3526656, ...}) = 0 pwrite64(8, "\0\0\0\0@\0\0\20\0\0\0\0\0\0\0\0$\0\0\0\0\0\0\0\1\0\0\0\200\200\200\214"..., 92, 32720) = 92 pwrite64(8, "\200\200\200\207", 4, 32720) = 4 fstat64(8, {st_mode=S_IFREG|0600, st_size=32812, ...}) = 0 pread64(8, "\200\200\200\207@\0\0\20\0\0\0\0\0\0\0\0$\0\0\0\0\0\0\0\1\0\0\0\200\200\200\214"..., 1024, 32720) = 92 pread64(8, "", 1024, 32812) = 0 stat64("/var/spool/indexes/ingoiwt/.wx-dev/dovecot.index", {st_mode=S_IFREG|0600, st_size=451180, ...}) = 0 fcntl64...

...02000, 1048576) = 0 munmap(0xFE302000, 1048576) = 0 munmap(0xFE202000, 1048576) = 0 munmap(0xFE102000, 1048576) = 0 munmap(0xFE002000, 1048576) = 0 munmap(0xFE000000, 8192) = 0 pread64(9, " n c o m @ o s s 1 >\n\0".., 8192, 7340032) = 8192 mmap64(0x00000000, 7364608, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFE800000 munmap(0xFDE04000, 1048576) = 0 munmap(0xFDD04000, 1048576) = 0 munmap(0xFDC04000, 1048576)...

...d=0, events=POLLIN|POLLPRI|POLLERR|POLLHUP|POLLNVAL}, {fd=1, events=POLLOUT|POLLERR|POLLHUP|POLLNVAL, revents=POLLOUT}], 4, 10000) = 1 gettimeofday({1238146847, 807077}, {0, 0}) = 0 write(1, "6DEDK02J5VXFQtloRQ/JPgdcCrSmSRXj"..., 2171) = 2171 setsockopt(1, SOL_TCP, TCP_CORK, [1], 4) = 0 pread64(9, "7P8JZloV9g/oYWdnm\nnZ9f+xzkO3fVXr"..., 4096, 102400) = 4096 write(1, "\r\nLhQoxZy+rq1TZXl2ZtrKrZH15dE2PK"..., 4134) = 3669 write(1, "uv69IdP6FDbO0lztPh2sA6Z/wBqIdP9Y"..., 465) = -1 EAGAIN (Resource temporarily unavailable) setsockopt(1, SOL_TCP, TCP_CORK, [0], 4) =...

...ght be the problem. If the binary is compiled in the 64bit environment and you want to use 64 bit file offset you must use 64 bit equivalents of the function. Of course if you are using open/pread (which are 32 bit compatible only) the whole program functionality will be broken. You must use open64/pread64 etc. Else macros _LARGE_FILE_API should be defined in order to use large files in other case nothing will work (random parsing errors and dead indexes will appear ). As I can see there is a big issue in the dovecot. http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm?info/apis/pread64.htm...

....def index 41cfa17..c56e8f9 100644 --- a/usr/klibc/SYSCALLS.def +++ b/usr/klibc/SYSCALLS.def @@ -189,8 +189,10 @@ int fdatasync,fsync::fdatasync(int); int readv(int, const struct iovec *, int); int writev(int, const struct iovec *, int); int ftruncate64,ftruncate::ftruncate(int, off_t); -ssize_t pread64,pread::pread(int, void *, size_t, off_t); -ssize_t pwrite64,pwrite::pwrite(int, void *, size_t, off_t); +<parisc> ssize_t pread64,pread::__pread(int, void *, size_t, off_t); +<parisc> ssize_t pwrite64,pwrite::__pwrite(int, void *, size_t, off_t); +<!parisc> ssize_t pread64,pread::...

I have a Fedora Core server running: Fedora Core release 4 (Stentz) kernel version: 2.6.15-1.1833_FC4smp ( I have also tried kernel version: 2.6.16-1.2108_FC4smp) I compiled the ocfs2 and ocfs2-tools using the following steps: # MODULES: tar zxvpf ocfs2-1.2.1.tar.gz cd ocfs2-1.2.1 ./configure make make install # TOOLS: tar zxf ocfs2-tools-1.2.1.tar.gz cd ocfs2-tools-1.2.1 ./configure

I downloaded 3.3.0 and tried compiling on Solaris 10 and got pretty far into the make before this message: Linking bin/smbd ./bin/libtdb.so: undefined reference to `write@SUNW_0.9' ./bin/libwbclient.so: undefined reference to `sleep@SUNW_0.7' ./bin/libtdb.so: undefined reference to `pread64@SUNW_1.4' ./bin/libtdb.so: undefined reference to `fcntl@SUNW_0.9' ./bin/libtalloc.so: undefined reference to `close@SUNW_0.9' ./bin/libtdb.so: undefined reference to `read@SUNW_0.9' ./bin/libtdb.so: undefined reference to `msync@SUNW_0.9' ./bin/libtdb.so: undefined reference to...

On 28 Mar 2019, at 10.15, Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote: > > error = 0x55e3e2b40ac0 "Fixed index file > /var/mail/piast_efaktury/dovecot.index: log_file_seq 13 -> 15", > nodiskspace = true, This was one of the things I was first wondering, but I'm not sure why it's not logging an error. Anyway, you're using filesystem quota? And this

How can I tell if this is normal behaviour? Oracle imports are horribly slow, an order of magnitude slower than on the same hardware with a slower disk array and Solaris 9. What I can look for to see where the problem lies? The server is 99% idle right now, with one database running. Each sample is about 5 seconds. I''ve tried setting kernel parameters despite the docs saying that