From: | avinash varma <avinashvarma443(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Pg_restore failed |
Date: | 2020-08-28 17:16:15 |
Message-ID: | CADaHE9EkayPPPN+bCDXS7ZyxjeDtMj7HnZuLBKM-0LVfcdx1Sw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Thanks Magnus.
Could you please point me if we have any supporting docs for postgres
recommended storage options.
Thanks,
Avinash
On Fri, Aug 28, 2020 at 10:39 PM Magnus Hagander <magnus(at)hagander(dot)net>
wrote:
>
>
> On Fri, Aug 28, 2020 at 6:55 PM avinash varma <avinashvarma443(at)gmail(dot)com>
> wrote:
>
>> Hi Team,
>>
>> Could you please help me with the below error msg. The same dump works
>> well with NFS storage. But it is failing with CIFS.
>>
>> pg_restore: error: could not execute query: PANIC: could not fdatasync
>> file "0000000100000001000000E9": Bad file descriptor
>> server closed the connection unexpectedly
>> This probably means the server terminated abnormally
>> before or while processing the request.
>> Command was: ALTER TABLE ONLY nsp_contact
>> ADD CONSTRAINT nsp_contact_casnum_constraint PRIMARY KEY (casnum);
>> --
>>
>> Below are error msgs from OS
>>
>> Aug 28 08:27:54 nid-2021-2 kernel: [ 1830.678930] CIFS VFS: No task to
>> wake, unknown frame received! NumMids 5
>> Aug 28 08:27:54 nid-2021-2 kernel: [ 1830.679229] 00000000: 23000000
>> 424d53ff 00000124 c00180c0 ...#.SMB$.......
>> Aug 28 08:27:54 nid-2021-2 kernel: [ 1830.679231] 00000010: 00000000
>> 00000000 00000000 3f230002 ..............#?
>> Aug 28 08:27:54 nid-2021-2 kernel: [ 1830.679233] 00000020: 01 00 b0 54
>> 00 ...T.
>> Aug 28 08:28:07 nid-2021-2 kernel: [ 1843.879397] CIFS VFS: No task to
>> wake, unknown frame received! NumMids 5
>> Aug 28 08:28:07 nid-2021-2 kernel: [ 1843.879698] 00000000: 23000000
>> 424d53ff 00000124 c00180c0 ...#.SMB$.......
>> Aug 28 08:28:07 nid-2021-2 kernel: [ 1843.879700] 00000010: 00000000
>> 00000000 00000000 00780002 ..............x.
>> Aug 28 08:28:07 nid-2021-2 kernel: [ 1843.879702] 00000020: 01 00 cd 7a
>> 00 ...z.
>> Aug 28 08:28:10 nid-2021-2 kernel: [ 1846.615625] CIFS VFS: Error -104
>> sending data on socket to server
>> Aug 28 08:28:10 nid-2021-2 kernel: [ 1846.615940] CIFS VFS: Error -32
>> sending data on socket to server
>> Aug 28 08:28:10 nid-2021-2 kernel: [ 1846.616147] CIFS VFS: Error -32
>> sending data on socket to server
>> Aug 28 08:28:10 nid-2021-2 kernel: [ 1846.616336] CIFS VFS: Error -32
>> sending data on socket to server
>> Aug 28 08:28:10 nid-2021-2 kernel: [ 1846.616546] CIFS VFS: Error -32
>> sending data on socket to server
>> Aug 28 08:28:10 nid-2021-2 kernel: [ 1846.616725] CIFS VFS: Error -32
>> sending data on socket to server
>> Aug 28 08:28:10 nid-2021-2 kernel: [ 1846.616911] CIFS VFS: Error -32
>> sending data on socket to server
>> Aug 28 08:28:10 nid-2021-2 kernel: [ 1846.617083] CIFS VFS: Error -32
>> sending data on socket to server
>> Aug 28 08:28:10 nid-2021-2 kernel: [ 1846.617253] CIFS VFS: Error -32
>> sending data on socket to server
>> Aug 28 08:28:22 nid-2021-2 kernel: [ 1859.070931] cifs_vfs_err: 11
>> callbacks suppressed
>> Aug 28 08:28:22 nid-2021-2 kernel: [ 1859.071232] CIFS VFS: Send error in
>> Flush = -9
>>
>>
> That is not a PostgreSQL problem, that is a kernel problem related to your
> cifs mount. You'll need to check that with the kernel people.
>
> That said, I would strongly advise you *not* to run PostgreSQL on a cifs
> mounted partition in general. This type of filesystem errors being one of
> the reasons for that.
>
> --
> Magnus Hagander
> Me: https://www.hagander.net/ <http://www.hagander.net/>
> Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
>
--
Thanks & Regards,
Avinash.
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2020-08-28 17:25:47 | Re: Pg_restore failed |
Previous Message | Magnus Hagander | 2020-08-28 17:09:17 | Re: Pg_restore failed |