Fix it already, so it was the SAN and vmware issue. Thanks Everyone.
On Fri, Jan 15, 2021 at 4:40 PM Soni M <diptat...@gmail.com> wrote: > More disk space now available, but still the error happens and postgres > won't start. > I think it could be corrupted shared buffers, as stated on the log > messages, and perhaps the corruption goes to disk. > > On Fri, Jan 15, 2021 at 4:33 PM Laurenz Albe <laurenz.a...@cybertec.at> > wrote: > >> On Fri, 2021-01-15 at 16:13 +0700, Soni M wrote: >> > We filled out the wal archive disk, and then those messages appear >> > >> > [...]PANIC,58030,"could not fsync file ""pg_wal/xlogtemp.3510"": >> Input/output error" >> > >> > And now I cannot start postgres >> > >> > [...]PANIC,58030,"could not fsync file ""pg_wal/xlogtemp.23229"": >> Input/output error" >> > >> > Any idea to solve this ? >> >> Did you add more disk space? >> >> You won't be able to start PostgreSQL unless you do that. >> >> And no, don't start deleting files in the data directory. >> >> What you can do is move the *complete* data directory to another location >> with more disk space and start it there. >> >> Yours, >> Laurenz Albe >> -- >> Cybertec | https://www.cybertec-postgresql.com >> >> > > -- > Regards, > > Soni Maula Harriz > -- Regards, Soni Maula Harriz
