Why would a file fail to open/close

Question

I am trying to include statements that instruct the user a little bit more about why a file failed to open or close. What are some possible situations where a file would fail to open in write mode and what about failing to close?

FILE *fp;

if(!(fp = fopen("testing", "w")))
    {
    fprintf(stderr, "\nError %d: Loading from \"testing\" file failed: %s\n",
    errno, strerror(errno));
    printf("Add additional explanations here\n");
    }

fclose(fp);

2nd: sharing (someone else is reading/writing without sharing) — Adriano Repetti, Dec 19 '13 at 23:00
if it's a network reasource it may be unavailable or timeout — Adriano Repetti, Dec 19 '13 at 23:01
@Adriano: (the sharing one) wouldn't that just block until the lock is released? — Humungus, Dec 19 '13 at 23:01
for absurd even not enough memory/resources to allocate required structure — Adriano Repetti, Dec 19 '13 at 23:01
errno just isn't nearly sophisticated enough. You'll have to dip down to the OS level to get a better diagnostic. Your CRT will have some way to bind the native file descriptor to the FILE or to report a better native error code. — Hans Passant, Dec 19 '13 at 23:01
@Humungus no, fopen() asks for an immediate access permission. — Adriano Repetti, Dec 19 '13 at 23:02
fclose()? file has been deleted (it depends on how you share your access) or you closed it before or buffer can't be flushed (all above errors plus disk space) — Adriano Repetti, Dec 19 '13 at 23:03
@Adriano Ok then... I think you gathered quite the number of reasons to form an answer. — Humungus, Dec 19 '13 at 23:03
@Humungus here it's almost time to sleep, I feel pretty lazy to write them down in a proper form (anyway true answer is...it's OS specific, check its documentation). I think most common are insufficient permissions and it doesn't exist. — Adriano Repetti, Dec 19 '13 at 23:05

score 2 · Answer 1 · answered Dec 19 '13 at 23:05

The error you can get from trying to open a file in write mode are OS specific. But it's basically that the owner or the user running the program don't have the rights to write to the file.

Same for the fclose, it's os specific but as it automatically execute a fflush, that is an operation that can fail when you don't have enough space on your disk for example.

score 1 · Answer 2 · answered Dec 19 '13 at 23:08

1

The fopen function is a system call. So the reason of a failure is heavily depending on your OS.

You can check which error happend by calling depending on your OS (getLastError() on Windows and errno on Linux). In addition, there is normally a header file on POSIX systems that maps the number to a reason, called errno.h.

Here as a example the linux man page regarding errno:

http://man7.org/linux/man-pages/man3/errno.3.html

answered Dec 19 '13 at 23:08

lwi

1,682
12
21

7

Always errno if he has to be portable. GetLastError() is Windows, **errno is C**. – Adriano Repetti Dec 19 '13 at 23:15

alk · Answer 3 · 2013-12-20T08:57:11.000

0

If fopen() fails and errno had been set EACCES it might be interessing to know for the user about the actual rights of the file in question, so in this case a call to stat() pulling those rights and displaying them to the user might be appropriate.

Also always log the file's name.

edited Dec 20 '13 at 08:57

answered Dec 20 '13 at 08:48

alk

69,737
10
105
255

score 0 · Answer 4 · edited Jun 20 '20 at 09:12

First of all, you could try using perror (see here).

Also, the list of errors of fopen is listed on its POSIX page: http://pubs.opengroup.org/onlinepubs/009695399/functions/fopen.html.

An extract of the above:

[EACCES] Search permission is denied on a component of the path prefix, or the file exists and the permissions specified by mode are denied, or the file does not exist and write permission is denied for the parent directory of the file to be created.

[EINTR] A signal was caught during fopen().

[EISDIR] The named file is a directory and mode requires write access.

[ELOOP] A loop exists in symbolic links encountered during resolution of the path argument.

In the end it all boils down if you want to print an error right away, or perhaps return it to a higher level to be parsed. Your user might not care/know what's a loop in symbolic links.

score -1 · Answer 5 · answered Oct 31 '17 at 00:49

Windows depends on the file extension to associate a data file with an application used to open it, which it calls the file association. An application associated with a file extension is called its default program. When you double-click a data file and Windows examines the file extension and doesn't know which application to call on to open the file, it displays an error message. The solution to this problem is to change the file association for the data file's file extension.

Windows does sure, but custom applications don't, you can call files whatever you want and then load them appropriately for your uses — Nick is tired, Oct 31 '17 at 01:18

Why would a file fail to open/close

5 Answers5