 
| Subject: | |
| From: | |
| Reply To: | |
| Date: | Tue, 15 May 2018 07:58:04 +0100 |
| Content-Type: | multipart/mixed |
| Parts/Attachments: |
|
|
On Tue, 15 May 2018, Lofgren, Eric wrote:
> Iâm running a SL 7 server thatâs being used for a couple data
> projects using MySQL Server - which I confess I donât know much
> about. Two have my students have both encountered errors recently,
> either joining tables or just restarting MySQL Server, with the logs
> reading things to the effect of:
>
> 2018-05-15T01:26:21.114290Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
> 2018-05-15T01:26:21.152895Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
> 2018-05-15T01:26:21.153010Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
> 2018-05-15T01:26:21.375361Z 0 [Warning] InnoDB: Retry attempts for writing partial data failed.
> 2018-05-15T01:26:21.375391Z 0 [ERROR] InnoDB: Write to file ./ibtmp1failed at offset 11534336, 1048576 bytes should have been written, only 643072 were written. Operating system error number 28. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
> 2018-05-15T01:26:21.375406Z 0 [ERROR] InnoDB: Error number 28 means 'No space left on device'
> 2018-05-15T01:26:21.375410Z 0 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
> 2018-05-15T01:26:21.375416Z 0 [ERROR2018-05-15T01:26:21.845562Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
> A quick check of whether or not thatâs genuinely a disk space problem using df -hT shows the following:
>
> [user@computer home]$ df -hT
> Filesystem Type Size Used Avail Use% Mounted on
> /dev/mapper/sl-root xfs 50G 50G 12M 100% /
> The database lives on /home, which doesnât seem anywhere near full,
> and the number of bytes that âshould have been writtenâ in that
> error message are nowhere near a threat to the capacity, which
> suggests something else might be going wrong.
>
> Does anyone have a notion of whatâs going on? My suspicion is that
> the problem is that the temporary file is just ./file, which is in
> the root directory, which as you can see *is* full - if this is the
> case, is there a way to redirect where those temporary files are
> made? Or should I just try to expand that?
The temp files have a relative path, so I guess they are in the current
working directory, which may be root's home directory.
If you cd to a directory with more space before starting, the temp
files may be made in that directory.
|
|
|
